Frequently asked questions

Where are notifications sent? To groups/topics connected by a Jira administrator and to users who separately opt in to personal messages.

Does every status change create a message? Stayposted normally edits one group card per issue. Nearby card updates are combined. Comments are separate messages and reply to the issue card when one exists.

How quickly do updates arrive? Delivery is asynchronous and depends on Jira/Forge and Telegram. In our latest 24-hour test (November 2026, 2,400 comments at 100 per hour) the median delay was 28 seconds, 95% arrived within 81 seconds and the slowest took about 9.5 minutes. These measurements are not a guarantee; retries and platform queues can take longer.

Does it work with Jira Service Management? Yes. Requests and public replies are delivered like other issues and comments. Internal notes, comments restricted to a role or group, and issues with a security level are never sent to groups.

Is there a limit on the number of groups or topics? No. You can connect as many Telegram groups and forum topics as you need and route each rule to one of them. Telegram's own rate limits still apply, so very busy setups may see longer delays.

What happens to private Jira content? Group delivery excludes issues with an issue-security level, internal JSM comments and comments restricted to a Jira role/group. Personal deliveries check the recipient’s current issue and comment access. Plain project permissions are not a membership check for every person in a Telegram group: the Jira administrator must choose an appropriate destination and rule.

Can former group members or people without Jira accounts read a delivered message? Anybody with access to the Telegram destination can read the content there. Telegram membership and Jira membership are separate. Do not connect a public or unsuitable group.

Are previous Telegram messages removed after access changes? No. Permission checks apply to new deliveries. Already delivered messages remain in Telegram until managed there. Copies, forwards and screenshots may also exist.

Can I respond or transition a task from Telegram? This release sends notifications and links back to Jira. It does not write changes or comments to Jira.

Why did I receive no DM for my own action? Stayposted suppresses your own actions. Have another authorized person assign or mention you for a positive check.

Can two Jira users share my Telegram account? One active Jira link per Telegram account and installation is supported. Linking another Jira account replaces the old link.

Why did my personal link disappear after an account/profile change? Atlassian can instruct the app to erase or refresh stored account data. Stayposted erases the associated records, including the link. If your account remains active, subscribe again to establish a fresh link.

Why is a group silent? Check the token, connected chat/topic, enabled rule, preview state, project/type/event match, subscription and delivery log. Security restrictions intentionally suppress some events. Use the Test button to distinguish a Telegram connection problem from a Jira rule/access issue.

What happens if the bot is removed or blocked? Telegram rejects delivery. Permanent access errors are recorded without endless retries for that delivery. Re-add/unblock the bot, verify the connection and generate a new event. Old permanently rejected notifications are not automatically replayed.

Can I replace the bot? Saving another bot identity disconnects chats, disables rules and removes personal links. Reconnect the new bot and ask users to subscribe again. Old Telegram messages belong to the old bot and remain there. Re-saving the same bot identity keeps the configuration.

How do I stop or delete data? Unsubscribe to stop DMs; disconnect a chat to disable its group rules. The personal page also offers deletion of app-managed account data. Jira content, Telegram history, and platform-managed queue/log retention are separate. An operation already sending to Telegram must finish before cancellation can be confirmed. If delivery or settings are busy, the page asks you to retry; do not treat an error as confirmation. A deletion interrupted by an infrastructure failure remains scheduled for retry. Already accepted Telegram messages cannot be recalled. Send a broader data request to the publisher’s privacy contact.

What does the price cover? Marketplace shows the subscription terms for your Jira installation. It does not count only Telegram subscribers. Confirm the displayed user tier before purchase. Telegram and Atlassian terms also apply.

What should I send support? Approximate UTC time, issue key, affected destination, event type and the relevant delivery-log reason. Remove issue/comment text if unnecessary. Never send bot tokens, API tokens or personal connection links.

Can I pause or edit a rule? Yes. An administrator can edit a rule or pause/resume it without deleting its configuration. A rule in preview still requires explicit delivery activation. If a rule changes while a delivery is queued, delivery checks the current destination and conditions again. A stale editor cannot overwrite a newer saved revision.

Can I receive only mentions? Yes. On Apps → Stayposted, keep only “I am mentioned” selected and save notification settings. You can independently enable assignments and changes to watched/assigned issues. Turning them all off preserves the Telegram link.

Can delivery ever repeat or fail? Yes. Telegram and Forge storage do not share a transaction. If Telegram accepts a message but its response or the subsequent storage write fails, a retry can create a duplicate. Some failures may prevent delivery. Stayposted must not be your only emergency notification channel.

An already-issued Telegram request can have an unknown outcome after a network timeout or crashed function. Its message may appear later even if you subsequently disconnect. Cancellation prevents new requests for stale settings; it cannot withdraw a request already sent to Telegram.