Connect and Manage Telegram Chats

The app uses the general term channel for every connected Telegram chat. A channel can be a Telegram channel, group, or supergroup. Every channel has its own projects, events, filters, status, and ticket-parsing setting.

Customers moving from the previous app can also create channels through the temporary Import wizard. Imported channels appear in the same Channels list and are managed like channels added manually.

Recommended method: verify with a command

1. On the Channels tab, select Add channel.

2. Keep Verify with command selected.

3. Add the configured bot to the required Telegram chat. For a channel, allow it to post.

4. Copy the complete command in the form /verify A1B2C3D4.

5. Send the command in the exact chat you want to connect.

6. Wait for Jira to show Connected.

7. Select Configure now to set routing rules immediately, or Later to return to the list.

The code contains eight alphanumeric characters and remains valid for five minutes. If it expires, select Regenerate code and send the new command. Do not reuse the old code.

The app rejects a chat that is already stored, whether it is active or inactive. Locate the existing row and activate or configure it instead.

Alternative method: ID, username, or link

Add by ID, username, or link is useful when you know the numeric chat ID, public @username, or public Telegram link. The bot must already be a member of the chat and be allowed to send messages.

1. Select the alternative method in the add dialog.

2. Enter a value such as @platform_alerts or a numeric supergroup ID.

3. Select Add channel.

4. The app requests the chat details from Telegram and verifies the bot's membership.

The recommended verification method is safer for private chats and does not require you to find a numeric chat ID manually.

The Channels list

The table displays the name, public username, type, member count, rule summary, and status. You can:

• search by name or @username;

• filter by channel, group, or supergroup;

• filter by active or inactive status;

• expand a row to inspect projects, events, ticket parsing, and the advanced-filter summary;

• use Configure and Remove;

• switch a channel between Active and Inactive.

Active and inactive channels

An active channel participates in Jira event routing and can use ticket parsing. An inactive channel receives no notifications, but its projects, events, and filters are preserved.

The product limit is five active channels per installation. Inactive rows do not count. When the limit is reached, deactivate one channel before activating or adding another. Use the Active channels counter shown by your installation as the operational reference.

Configure a channel

Select Configure. The dialog contains:

• the overall Active switch;

• Jira projects — all projects or a selected set;

• Event types — Jira events allowed for delivery;

• Ticket parsing — Jira-key replies in groups and supergroups;

• Advanced filters — nested rules based on issue fields.

Changes take effect only after you select Save changes. See Configure Jira Notifications: Projects, Events, and Filters for the complete routing logic.

Remove a channel

Remove permanently deletes the channel row and its projects, events, ticket-parsing setting, and advanced filters. It does not remove the bot from the Telegram chat. To restore the channel, connect it again and rebuild its configuration.

Automatic availability checks

The app periodically checks whether the bot is still a member of connected chats. The current Forge configuration runs the complete check once a week. In addition, a permanent send error indicating that the bot was removed deactivates the channel. After restoring the bot, verify its permissions and activate the channel manually.