Frequently Asked Questions
Answers about migration import, customer-owned bots, supported events, channel limits, advanced filters, ticket parsing, security, and the current Forge Edition feature set.
- Last verified
- Product
- Vivid Connector
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.
Can we import settings from the previous Vivid Connector app?
Yes, temporarily. Connect the Forge bot, then open Import. The app automatically checks for supported data belonging to the same Jira base URL. You can review and select channels before any write occurs. See Import Settings from the Previous Vivid Connector App.
What is not copied by the import?
The wizard copies only current end-to-end Forge features: channels, active state, projects, supported events, compatible filters, and Jira-key parsing. It reports unsupported historical message format, mode, or comment settings. Existing Forge channels are never overwritten.
Which Telegram chat types are supported?
Telegram channels, groups, and supergroups are supported as connector channels. Ticket parsing is supported only in groups and supergroups.
How many channels can we connect?
The product limit is five active channels per installation. Inactive channels keep their settings and do not count. The Jira UI shows the limit and current active count for the installation.
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. Use the explicit move-up and move-down controls to reorder items.
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, the channel is active, and the bot can read ordinary messages. Make it an administrator, or disable Group Privacy in @BotFather and then remove and re-add the bot.
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 Forge edition.
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.
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.
VIVID INSIGHT