Connect and Manage Telegram Chats

The app uses the general term channel for every connected Telegram destination. A channel can be a Telegram channel, group, supergroup, or one specific topic in a supergroup where Topics are enabled. Every destination has its own projects, events, filters, status, and ticket-parsing setting.

Topics in the same supergroup are independent channels in Jira. Connecting one topic does not route notifications to the group root or another topic, and settings saved for one topic do not affect the others.

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 or topic you want to connect. For a forum topic, open that topic before sending the command.

6. Confirm that the bot's Connected response appears in the same chat or topic.

7. Wait for Jira to show Connected.

8. 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 an exact destination that is already stored, whether it is active or inactive. In a forum group, the root and each topic are different destinations, so multiple topics from the same group can be connected separately.

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.

For a forum group, this alternative method connects only the group root. It cannot identify a topic because a chat ID, username, or link does not include Telegram's message-thread ID. To connect a topic, use the recommended command method inside that topic.

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, topic label when applicable, type, member count, rule summary, and status. A connected topic is shown as the group name plus the observed Telegram topic name, for example Engineering / Deployments. Telegram exposes topic names to bots through topic service messages rather than a dedicated lookup method, so Topic #42 remains the fallback until the bot observes the name. New connections normally capture the name from the verification message. For a topic connected by an older app version, send a new verification command in that topic or rename it, then reload Channels.

• 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 current release does not apply a fixed app-level cap to active channels. Each group root and forum topic remains an independent destination with its own status and configuration. Inactive rows keep their settings, and the Active channels counter remains an informational view of the installation.

After verification, a new channel is created for all Jira projects with Issue created, Issue updated, and Comment created selected. Ticket parsing is off. Review and save the configuration before relying on production delivery; Comment updated and Comment deleted are available but are not selected by default.

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;

• JSM comment visibility — public customer replies, private internal notes, or both;

• Notification grouping — whether matching events are sent separately or collected into a 60-second summary;

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

• Advanced filters — nested rules based on issue fields and the Action author.

Both JSM comment visibility options are enabled by default. The selection applies to comment creation, updates, and deletion in Jira Service Management only; comments in other Jira projects are unchanged. Clear both options to stop JSM comment notifications for this destination while leaving its other event types active.

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

After the topic-aware database update, groups connected by an earlier app version remain root destinations with their existing configuration. Connect any required topics separately with a new verification command.

Remove a channel

Remove permanently deletes only the selected root or topic row and its projects, events, ticket-parsing setting, and advanced filters. Other topics from the same group are not changed. Removing a row does not remove the bot from the Telegram chat.

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.

Notification grouping

Notification grouping is off by default. Each channel or Topic can group matching events by action author, or by action author and issue. The first matching event opens a fixed 60-second collection window. The summary is sent when it closes, even for one event; later events do not restart the timer, and Telegram limits can add delay. JSM comment visibility is checked again before delivery, so comments disabled during the wait are removed while other allowed actions remain in the summary.