Migrate to Vivid Connector for Jira and Telegram (Forge Edition)

We rebuilt Vivid Connector for Jira and Telegram on Atlassian Forge. The new app is called Vivid Connector for Jira and Telegram (Forge Edition).

If your team currently uses the previous app, install the Forge edition separately and connect a new customer-owned Telegram bot. Supported previous-app settings may be imported after the new bot is connected, but unsupported or conflicting settings must be recreated manually. We understand that this creates additional work, and we are sorry for the inconvenience. This guide explains what is changing and how to migrate with as little disruption as possible.

Important deadline: August 31, 2026

The previous Vivid Connector for Jira and Telegram app by VIVID INSIGHT UNIPESSOAL LDA will stop working on August 31, 2026.

Complete your migration well before this date. Do not uninstall the previous app until the Forge edition is fully configured and tested.

Install Vivid Connector for Jira and Telegram (Forge Edition) from Atlassian Marketplace.

Why this is happening

The previous Vivid Connector for Jira and Telegram was built on Atlassian Connect. Atlassian has since moved its app-platform direction to Forge, and updates to the legacy Connect app are no longer being processed as expected.

As a result, we can no longer reliably maintain or publish updates for the previous app. We delayed this migration for as long as reasonably possible, but rebuilding on Forge is now necessary to keep the product maintainable and reliable.

Because the Forge edition uses a fundamentally different architecture, the app installation and Telegram bot cannot be transferred automatically. The temporary Import tab can copy supported settings discovered for the same Jira site. Anything that the Forge edition cannot represent safely must be reviewed and configured manually.

What stays the same

The Forge edition continues to provide the core integration between Jira Cloud and Telegram:

• Jira event notifications can be sent to Telegram.

• Jira-key parsing remains available in Telegram groups. When someone mentions a Jira issue key, the app can find the relevant issue and display its details.

• The required permissions remain the same.

• Our data-processing approach remains the same.

• The price does not change.

• Atlassian continues to manage licensing and billing, with no changes from our side.

What changes

• The Forge edition has a separate Atlassian Marketplace listing.

• The Forge edition must be installed separately, and each customer connects a customer-owned Telegram bot instead of using one shared bot.

• Supported channels, project selections, event selections, compatible filters, active state, and Jira-key parsing settings can be imported when previous-app data is available. Other settings must be recreated manually.

• The Forge edition includes more advanced notification filtering, including nested AND/OR rules.

• Each Jira installation can have up to five active Telegram channels. Inactive channels preserve their configuration and do not count toward this limit.

• Not every legacy feature is included in the current Forge release. We will collect feedback and prioritize missing functionality, improvements, and fixes based on customer needs. We are not setting a timeline for restoring every legacy feature.

How to migrate

To minimize disruption, configure and test the Forge edition before removing the previous Connect app.

1. Install the Forge edition

Install Vivid Connector for Jira and Telegram (Forge Edition) from its Atlassian Marketplace listing on the same Jira Cloud site that uses the previous app.

2. Create and connect your Telegram bot

Create a Telegram bot for your organization using @BotFather, then connect it to the Forge edition. Follow the installation and bot setup guide.

3. Import supported settings

After the new bot is connected, open the temporary Import tab. The app checks for supported previous-app data belonging to the same Jira site. Review the discovered channels and parsing groups, select what you want to copy, and complete the Telegram access checks.

Import does not overwrite a channel already configured in Forge. It also enforces the five-active-channel limit. See Import Settings from the Previous Vivid Connector App for the complete list of supported settings and manual-setup cases.

If no supported data is found, or a setting is marked as requiring manual setup, recreate the required channel, project, event, parsing, and filter configuration manually.

4. Review and complete your configuration

Review every imported channel and recreate anything that was not imported, including:

• Jira notification rules and project selections;

• notification filters;

• Telegram channel configuration;

• Jira-key parsing settings;

• any other required app settings available in the current Forge release.

5. Test the new setup

Confirm that:

• expected Jira event notifications reach the correct Telegram channels;

• notification filters behave as intended;

• Jira issue keys mentioned in configured Telegram groups can be found and their details displayed;

• your most important day-to-day workflows operate as expected.

6. Disable notifications in the previous app

After the Forge edition is working correctly, disable notifications in the previous Vivid Connector for Jira and Telegram app. This helps prevent duplicate Telegram messages while you complete the transition.

7. Uninstall the previous app

Only after the new configuration has been fully verified, uninstall Vivid Connector for Jira and Telegram by VIVID INSIGHT UNIPESSOAL LDA.

Important: Do not uninstall the previous app before the Forge edition is configured and tested. Removing it too early may interrupt your Jira-to-Telegram notifications.

Migration checklist

• [ ] Install Vivid Connector for Jira and Telegram (Forge Edition).

• [ ] Create a customer-owned Telegram bot using @BotFather.

• [ ] Connect the new bot to the Forge edition.

• [ ] Use Import to copy supported previous-app settings, when available.

• [ ] Recreate and review notification rules, filters, settings, and channel configurations.

• [ ] Test Jira event notifications.

• [ ] Test Jira issue-key lookups from configured Telegram groups.

• [ ] Disable notifications in the previous Connect app.

• [ ] Confirm that duplicate messages are not being sent.

• [ ] Uninstall the previous app only after the new setup is working.

• [ ] Complete the migration before August 31, 2026.

Need help?

Support is available through @JTNSupport on Telegram. We will do our best to help with installation, bot connection, configuration, and migration questions. Please note that replies may not be immediate.

We also welcome feedback about missing legacy functionality, improvements, and issues. We will review this feedback and prioritize future work based on customer needs. Never send your Telegram bot token or complete webhook URL to support.

FAQ

Why do I need to migrate?

The previous app was built on Atlassian Connect. Atlassian has moved its app-platform direction to Forge, and we can no longer reliably maintain or publish updates for the Connect-based app. We rebuilt the product on Forge so that it can remain maintainable and reliable.

When will the previous app stop working?

The previous Vivid Connector for Jira and Telegram will stop working on August 31, 2026. Migrate well before the deadline so your team has enough time to configure and test the Forge edition.

Will my settings be migrated automatically?

Not completely. You must install the Forge edition and connect a customer-owned Telegram bot manually. After that, the temporary Import tab can copy supported settings discovered for the same Jira site. Unsupported, conflicting, or unavailable settings must be recreated manually.

Will the price or licensing change?

No. The price does not change, and Atlassian continues to manage licensing and billing. There are no changes from our side.

Are permissions or data processing changing?

No. The required permissions and our data-processing approach remain the same.

What features are available in the Forge edition?

The current Forge edition includes:

• Jira event notifications to Telegram;

• Jira issue-key parsing and issue detail lookups in configured Telegram groups;

• advanced notification filtering with nested AND/OR rules;

• support for customer-owned Telegram bots;

• independent channel configuration and more direct control over the Telegram integration;

• up to five active Telegram channels per Jira installation, with inactive configurations preserved.

Not every legacy feature is included in the current Forge release. Review Security, Data Handling, and Current Release Scope before migration. We will review customer feedback and prioritize missing functionality, improvements, and fixes based on customer needs.

Why do I need to create my own Telegram bot?

The Forge edition uses customer-owned Telegram bots instead of one shared bot. This gives your organization more direct control over its Telegram integration. Follow the installation and bot setup guide.

How many Telegram channels can I configure?

Each Jira installation can have up to five active Telegram channels. Inactive channels preserve their configuration and do not count toward the limit.

What happens if I do not migrate before the deadline?

The previous app will stop working on August 31, 2026. If you have not completed the migration, the Jira-to-Telegram workflows provided by the previous app will no longer operate. To avoid disruption, install, configure, and test the Forge edition before the deadline.

Where can I get support?

Contact @JTNSupport on Telegram. Replies may not be immediate, but we will assist as soon as possible.

Thank you for using Vivid Connector. We recognize that this migration creates extra work, and we sincerely apologize for the inconvenience. We appreciate your patience and will work to make the transition as practical as possible.