Import Settings from the Previous Vivid Connector App

The temporary Import tab helps customers who used the previous Vivid Connector app recreate supported settings in Forge. If this is your first installation, you do not need to import anything and can configure channels normally.

The tab appears after the Forge Telegram bot is connected. Jira checks for previous-app data when the settings page loads, without waiting for you to open Import. If supported data is available, the tab label shows how many channels can be imported.

How Jira sites are matched

The Forge backend reads the canonical URL of the current Jira site and asks the read-only previous-app service for the matching installation. You cannot type or replace this URL in the browser. A match is made only for the same normalized Jira base URL.

If no match is found, Import explains whether the previous app has no tenant for this Jira URL, the tenant has no supported settings, import is not configured, authentication was rejected, or the service is temporarily unavailable.

What the wizard can import

• Telegram notification channels, groups, and supergroups;

• active or inactive status;

• selected Jira projects;

• supported issue and comment event types;

• compatible flat filter conditions joined entirely by AND or entirely by OR;

• standalone Jira-key parsing groups and parsing enabled on a matching notification group.

An empty imported event selection sends no notifications. Legacy comment-creation settings are stored as comment_created.

Settings unavailable in the current Forge edition, such as the historical message format, mode, or comment visibility options, are not imported. The Review step names these omissions. Legacy equality, inequality, contains, does-not-contain, greater-than, and less-than filters can be converted. Greater-than-or-equal, less-than-or-equal, in, and not-in filters require manual setup.

A channel is marked Needs manual setup when copying it would change behavior. Examples include notification delivery and Jira-key parsing that used different project lists, or a legacy Jira project that was deleted or is no longer accessible. Forge resolves stored numeric project IDs to their current Jira keys, so a project rename does not by itself prevent import.

Step 1. Review and select

1. Connect the new Forge Telegram bot.

2. Open Import.

3. Review every discovered channel, project selection, event selection, filter summary, and Jira-key parsing state.

4. Clear the checkbox for anything you do not want to import.

5. Select Check selected channels.

A Telegram channel already present on the Forge Channels tab is displayed as Already configured. Import never overwrites it.

The limit is five active Forge channels, including channels that already exist. Inactive imported channels keep their configuration and do not count toward this limit.

Step 2. Check the new bot

The new bot must be present and ready in every selected Telegram channel:

• in a channel, make the bot an administrator and allow it to post messages;

• in a group or supergroup, add the bot and allow it to send messages;

• for Jira-key parsing, make the bot an administrator or disable Group Privacy in @BotFather and re-add the bot.

Import selected remains unavailable while any selected row shows Action required. Correct the Telegram setup and select Refresh checks, or clear that channel's checkbox.

Step 3. Import and review the report

Immediately before saving, Forge reloads the previous-app data, compares each selected configuration with the version you reviewed, and repeats the Telegram checks. If the old settings changed, the wizard returns to Review instead of importing unconfirmed data. This also prevents a recently removed permission from being imported.

The final report marks every channel as Imported, Skipped, or Failed and explains the result. Successfully imported channels appear on Channels. Review them there before generating a production Jira event.

Parse-only groups

A previous standalone parse chat is imported as a Forge group with Jira-key parsing enabled and no notification events. Its previous project selection controls which Jira keys can receive replies. Because zero selected events sends nothing, the group does not begin receiving Jira event notifications accidentally.

If nothing is found

No action is required for a new customer. For an existing customer, confirm that the Forge app is installed on the same Jira site used by the previous app, then select Check again. If the service reports authentication or configuration errors repeatedly, contact support with the displayed message and time, but never include a Telegram bot token.