Telegram Notifications: Alerts & Reports for Jira
Send Jira issue updates and scheduled JQL reports to Telegram chats.
Get it on the Atlassian Marketplace →
Overview
Keep a team up to date where it already talks. Connect your own Telegram bot and choose what reaches each group or channel: new issues, status or assignee changes, comments or other field changes, per project and JQL. Schedule daily or weekly reports of any JQL query.
- Rules by project, kind of change and JQL filter, each one sending to a chat.
- Messages with the issue, what changed, who changed it and a link to Jira; comment text is optional.
- Daily or weekly reports with the issues of a JQL query and a link to the full search.
- Your own bot: its token is stored encrypted and never shown again.
Getting started
- A Jira administrator installs the app from its Atlassian Marketplace listing.
- In Telegram, open @BotFather, send
/newbotand follow the steps. Copy the token it gives you. - In Jira, open Settings → Apps → Telegram notifications. In the Bot tab, paste the token and select Connect.
- Add the bot to a group (or as an administrator of a channel). In the Chats tab, select Find chats, then Save and Send test.
- In the Rules tab, select Add rule. Reports are set up in the Reports tab.
Rules
| Setting | What it does |
|---|---|
| Projects | The projects the rule applies to. Empty means all projects. |
| Send a message when | Issue created, status changed, assignee changed, comment added, other fields changed. |
| Only issues matching this JQL | Optional filter, for example priority in (High, Highest). It is checked when the change happens. |
| Chat | Where the message goes. |
| Include the comment text | When a comment is added, the first 300 characters are included. |
Reports
A report sends the issues of a JQL query to a chat every day or every week at the time you choose, in the time zone of the administrator who saved it. It lists up to 50 issues and links to the full search. Send now sends it at once.
Moving from Telegram Connector for Jira
Telegram Connector for Jira is an app for Data Center. Atlassian Data Center reaches end of life on 28 March 2029, so if you are moving to the cloud, this app covers the same needs in Jira Cloud.
The configuration of the other app is not copied. Set this app up in a few minutes (see Getting started):
- Create a new bot with @BotFather, so that the Data Center app and this app do not share one bot while both are running.
- Recreate the event notifications as rules: projects, kind of change, JQL and chat.
- Recreate the scheduled reports as reports.
If you use the Jira Cloud Migration Assistant, you can choose this app as the cloud alternative to Telegram Connector for Jira when you assess your apps.
Limitations
- Telegram keeps a bot's updates for 24 hours: after adding the bot to a chat, use Find chats within a day.
- Everyone in a chat sees its messages, including people who cannot open the project in Jira. Choose chats and JQL filters with that in mind.
- The app reads issues as itself, so a rule can notify about issues in any project the app can see.
Permissions
| Scope | Why |
|---|---|
storage:app | Store the rules, the chats and the bot token (encrypted). |
read:jira-work | Read the changed issue, check the JQL of a rule and search the issues of a report. |
read:jira-user | Show the name of the person who made the change. |
api.telegram.org | The only external service: the Telegram Bot API, to send the messages. |
Data and privacy
The app stores the bot token (encrypted), the chats you save (ID and name) and the rules and reports (projects and JQL) in Atlassian's Forge storage. When a rule or report matches, it sends to Telegram the issue key, summary, status, the names of the people involved and, if you choose, the comment text. Those messages are then kept by Telegram under its own terms. See the privacy policy.
Troubleshooting
Find chats finds nothing
Add the bot to the group again, or send a message in the group mentioning the bot, then try again. For a private chat, send /start to the bot.
Messages stopped arriving
The bot may have been removed from the chat or its token revoked in @BotFather. Connect the bot again in the Bot tab and check the chat with Send test.
The app says it needs an active license
The app is paid and checks the license on every request. Ask your site administrator to check the app's subscription in the administration of Jira or Confluence (Apps → Manage apps). During a free trial the app works normally.
Need help?
See the support page.