VIVID INSIGHT
Browse Vivid Connector documentation
Guide

Vivid Connector for Jira and Telegram

Connect your own Telegram bot to Jira Cloud, route events to channels and groups, configure projects, event types, and nested filters, and reply with issue details when Jira keys are mentioned.

Last verified
Product
Vivid Connector

Vivid Connector for Jira and Telegram (Forge Edition) connects Jira Cloud to Telegram channels, groups, and supergroups 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.

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.

Important: this documentation describes the current Forge edition. After a new bot is connected, a temporary Import wizard can copy supported channels, parsing groups, projects, events, and compatible filters from the previous app. Personal Telegram notifications, Jira-to-Telegram user linking, due-date reminders, creating Jira comments from discussion groups, and editable notification templates are not currently available in the user interface.

What the current version can do

  • use a customer-owned Telegram bot;

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

  • discover and selectively import supported settings from the previous app for the same Jira site;

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

  • connect Telegram channels, groups, and supergroups using a temporary command or a chat identifier;

  • activate and deactivate channels without losing their settings;

  • configure an independent set of Jira projects and event types for every channel;

  • 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 messages and reply with issue details;

  • 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 or group never change the settings of another.

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. Create a Telegram bot with @BotFather and keep the issued token secure.

  2. Open the Vivid Connector 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. If you used the previous app, open Import, review the discovered data, and complete the Telegram access checks. Otherwise continue to Channels.

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

  7. Add the bot to the required Telegram chat and send the displayed /verify XXXXXXXX command there.

  8. After verification, select Configure now.

  9. Choose projects and events, then add advanced filters or enable ticket parsing for a group if required.

  10. 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, imports or 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.