VIVID INSIGHT
Product 01

Vivid Connector for Jira and Telegram

Connect Jira Cloud to Telegram channels, groups, and supergroups through a bot your organization owns. Administrators control where notifications go, which Jira events are included, and which issues must pass additional filters.

Jira CloudAtlassian ForgeTelegram Bot API
View documentationStart with the guide
SourceJira Cloud
Forge appVivid Connector
  • Per-chat rules
  • Delivery status
DestinationTelegram
Customer-owned bot · independent configuration per chat
Overview

Move Jira signal into the chats where teams coordinate

Vivid Connector is a focused Forge app for organizations that use Jira Cloud for work tracking and Telegram for day-to-day coordination. It delivers readable Jira issue and comment events into selected Telegram chats without creating another workflow or source of truth.

Every connected chat is configured independently. Administrators can choose projects and event types, apply nested AND/OR filters, review recent processing outcomes, and enable Jira-key lookup in groups. The current release does not create Jira comments from Telegram replies or send personal Telegram notifications.

Capabilities

What the current product provides

  • 01 / CONTROL

    Customer-owned Telegram bot

    Your organization creates and controls the Telegram bot. The token is stored in Forge secret storage and is never returned to the browser.

  • 02 / ROUTING

    Independent rules per chat

    Each Telegram channel, group, or supergroup has its own active state, Jira projects, event types, and optional advanced filter.

  • 03 / EVENTS

    Precise event selection

    Choose issue-created, issue-updated, and supported comment events independently for each connected chat.

  • 04 / FILTERS

    Nested AND/OR filters

    Build two-level filter groups that evaluate Jira issue fields after project and event checks.

  • 05 / LOOKUP

    Jira-key lookup in groups

    When enabled, the bot recognizes Jira keys in Telegram group messages and replies with the issue details available to the app.

  • 06 / OPERATIONS

    Observable, resilient delivery

    Recent activity records routing outcomes while deduplication, rate-aware pacing, and retries protect message delivery.

Documentation

Plan, configure, and operate the connector

Documentation is maintained in Contentful and organized around the product lifecycle.

01

Overview

Start with product scope, requirements, and the end-to-end processing flow.

1 page
02

Setup

Install the app, connect the bot, import supported settings, and add Telegram chats.

3 pages
03

Configuration

Control projects, events, advanced filters, notifications, and Jira-key lookup.

2 pages
04

Operations

Monitor delivery, troubleshoot behavior, and understand security and current release scope.

3 pages
Browse all documentation