Frequently Asked Questions

How do we install the app?

Install Vivid Connector for Jira and Telegram from its Atlassian Marketplace listing on your Jira Cloud site.

Do we need our own Telegram bot?

Yes. Your organization creates and controls its own bot through @BotFather. One bot token is configured for one app installation.

Who can configure the app?

Configuration is exposed on a Jira administration page, so a Jira administrator performs the setup. Adding the bot also requires the appropriate permissions in each Telegram chat.

Which Telegram chat types are supported?

Telegram channels, groups, supergroups, and individual topics in forum-enabled supergroups are supported as connector channels. Ticket parsing is supported only in groups and supergroups, including independently connected topics.

How many channels can we connect?

The current release has no fixed app-level cap on active channels. Every group root and forum topic is configured independently, and inactive channels keep their settings. The Jira UI shows the current active-channel count for the installation.

Can different topics in one group use different settings?

Yes. Connect each topic by sending a separate verification command inside it. Every topic then has its own Active state, Jira projects, event types, advanced filters, and Ticket parsing setting. Adding the group by ID, username, or link connects only the root.

What happens if every Event types checkbox is cleared?

The channel receives no Jira event notifications. An empty event selection means “send nothing,” not “send everything.”

What happens if Selected projects is enabled without a project?

No issue passes the project filter. Select All projects explicitly when you want to allow every project.

Which Jira events are supported?

Issue created, Issue updated, Comment created, Comment updated, and Comment deleted. The identifier for comment creation is comment_created.

Can one event be sent to several chats?

Yes. The connector evaluates every active channel independently and sends a message to each matching channel.

Can notifications be paused without deleting the configuration?

Yes. Set the channel to Inactive. Its projects, events, and advanced filters are preserved.

Can we customize notification text?

Not through the current admin UI. The delivery flow uses built-in layouts, and a customer-facing template editor is unavailable.

How do advanced filters work?

Rules are combined into AND/OR groups, and those groups are combined with root-level AND/OR logic. The builder supports two nesting levels and up to ten items in a group. Is one of and Is not one of compare a field with up to 50 separately entered values, ignoring case and surrounding whitespace; a comma inside one row stays part of that value. Use the explicit move-up and move-down controls to reorder rules and membership values.

Why does an Assignee filter not match?

Use the user's display name or correct Jira account ID. The connector attempts to enrich user fields through the Jira API, but a deleted field, unavailable issue, or permanent API error can cause the notification to be skipped.

Why does the bot not recognize a Jira key in a group?

Confirm that Ticket parsing is enabled for the exact root or Topic row, that row is active, and the bot can read ordinary messages. A topic does not inherit parsing from another destination. Make the bot an administrator, or disable Group Privacy in @BotFather and then remove and re-add it.

How many keys can one message contain?

The app processes the first three unique Jira keys. Nonexistent, unavailable, and disallowed-project issues are ignored silently.

Does a Telegram reply create a Jira comment?

No. Bidirectional comment synchronization and discussion-group integration are unavailable in the current release.

Are personal notifications and due-date reminders available?

No. The current release does not link Telegram users to Jira and does not send personal direct messages or due-date digests.

Where is the bot token stored?

It is stored in Forge secret storage. The browser receives only a masked value. If the secret is exposed, revoke it through @BotFather and configure a new one.

What happens when a channel is removed?

The app permanently deletes the channel and its rules from its database, but it does not remove the bot from the Telegram chat. Restoring the channel requires a new connection.

What happens if the Marketplace subscription is inactive?

Configuration actions, Jira notifications, scheduled checks, and Telegram processing are paused until the license becomes active again. Saved bot and channel configuration is not automatically deleted.

What happens when the bot token is removed?

The app removes the bot token, webhook registration data, and webhook secret, so delivery and Telegram commands stop. Saved channels and their projects, events, filters, active state, and ticket-parsing settings remain available for review after another bot is connected.

Where can we check a delivery result?

Open Overview and review Recent activity. It shows the ten latest channel-routing and delivery outcomes.

Where can we get help?

Start with the monitoring and troubleshooting guide. If the problem remains, contact @JTNSupport on Telegram without sharing the bot token or complete webhook URL.