VIVID INSIGHT
Browse Vivid Connector for Jira and Telegram documentation
Guide

Vivid Connector for Jira and Telegram

Connect Jira Cloud to Telegram with a customer-owned bot, independent channel and topic settings, advanced notification filters, and Jira-key parsing.

Last verified
Product
Vivid Connector for Jira and Telegram

Vivid Connector for Jira and Telegram (Forge Edition) connects Jira Cloud to Telegram channels, groups, supergroups, and individual forum topics through a bot owned by your organization. A Jira administrator controls where notifications are sent, which projects and events are included, and which issues must pass additional filters.

Vivid Connector for Jira and Telegram is now available as a paid Atlassian Marketplace app. An active subscription is required for production configuration, notification delivery, scheduled checks, and Telegram request processing.

Telegram receives a concise, readable event message with a View in Jira button. In groups, the bot can also reply with issue details when a participant mentions a key such as PLAT-2841.

The current release provides channel and group notifications, independently configured forum topics, advanced filters, and Jira-key parsing. Personal Telegram notifications, Jira-to-Telegram user linking, due-date reminders, creating Jira comments from Telegram replies, and editable notification templates are not included.

What Vivid Connector for Jira and Telegram can do

  • use a customer-owned Telegram bot;

  • validate the bot token with Telegram and register the webhook automatically;

  • keep configuration unavailable while required database updates are pending and let an administrator run them from the page;

  • connect Telegram channels, groups, supergroups, and individual topics using a temporary command;

  • activate and deactivate channels without losing their settings;

  • configure an independent set of Jira projects, event types, filters, and ticket-parsing behavior for every root or topic destination;

  • support nested filter groups with AND/OR logic;

  • send issue-created and issue-updated events, plus comment-created, comment-updated, and comment-deleted events;

  • show the latest event-processing results in Recent activity;

  • recognize Jira keys in Telegram group or topic messages and reply in the same destination;

  • protect delivery against duplicates, pace messages per Telegram chat, and retry temporary failures.

How an event is processed

  1. Jira sends the connector an issue or comment event.

  2. The connector considers active channels only.

  3. For each channel, it checks whether the event type is enabled.

  4. It then checks the issue's project.

  5. If configured, it evaluates the nested advanced filter.

  6. A separate Telegram message is prepared for every matching channel.

  7. The message is queued, sent with rate-aware pacing, and recorded in Recent activity.

If an event matches two channels, both receive the message. Settings for one channel, group root, or topic never change the settings of another, including another topic in the same supergroup.

Requirements

  • Jira Cloud with Vivid Connector for Jira and Telegram (Forge Edition) installed;

  • Jira administrator access to the app configuration page;

  • a Telegram account allowed to add a bot to the required channels or groups;

  • a customer-owned bot created with @BotFather;

  • permission for the bot to post in a Telegram channel;

  • permission for the bot to read ordinary group messages when ticket parsing is required.

Quick start

  1. Install Vivid Connector for Jira and Telegram from Atlassian Marketplace and create a Telegram bot with @BotFather; keep the issued token secure.

  2. Open the Vivid Connector for Jira and Telegram configuration in Jira. If Database update required appears, select Run database updates and wait for settings to unlock.

  3. Select Connect bot.

  4. Paste the token. The app validates it and registers the Telegram webhook.

  5. For a new channel, open the Channels tab and select Add channel.

  6. Add the bot to the required Telegram chat. To connect a forum topic, open that topic and send the displayed /verify XXXXXXXX command inside it.

  7. After verification, select Configure now.

  8. Choose projects and events, then add advanced filters or enable ticket parsing for the connected group root or topic if required.

  9. Save the configuration and verify delivery with a controlled Jira event.

Documentation sections

Who can access the settings?

The app is exposed as a Jira administration page. A Jira administrator configures the token, adds channels, and manages routing rules. Telegram participants do not need to install the app or link personal accounts: they receive messages in a connected chat and, when ticket parsing is enabled, can mention Jira keys available to that channel.

Need help? Contact your Jira administrator or @JTNSupport on Telegram.