Transition Jira Issues With One Telegram Button Tap
Approvals shouldn't require opening Jira. Tap the button. Done.
Trigger
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Action
Transition Issue
Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.
Why this helps
Review requests languish because clicking them open in Jira feels like friction. Telegram is always open; Jira isn't.
- Approve work without leaving Telegram
- Instant workflow state changes
- Reduces approval bottlenecks
Setup
Build it in a few focused steps.
- 1Connect Telegram and Jira integrations in Notis (portal setup).
- 2Create an automation: 'Send me a Telegram button to move a Jira issue to the next workflow state'.
- 3Notis adds inline keyboard buttons to its Telegram messages, triggered when a 'Callback Query' (button tap) occurs.
- 4Set your notification channel for confirmation that the issue transitioned.
- 5Test by tapping a button in a Notis message—the Jira issue moves through the workflow.
Questions about this workflow
Can I use multiple buttons for different transitions?
Yes. Notis can offer multiple workflow options (e.g., Approve, Request Changes, Close) as separate buttons.
Does the issue move in real time?
Yes. Tapping the button immediately transitions the Jira issue and sends confirmation back to Telegram.
What if someone taps by accident?
Notis can add a confirmation step or use reversible transitions—e.g., moving from 'Approved' back to 'In Review'.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Jira. A trigger fires from one place; an action lands in another.
Telegram triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Telegram and Jira, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Jira.