Update Jira Issue Priority From Telegram Keywords

Write URGENT in Telegram. Jira issue gets marked critical. That's it.

Trigger

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.

Jira logo

Action

Edit Issue

Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.

Why this helps

Priority markers live in Telegram messages ('this is critical!'), but Jira fields stay at default. Priorities get missed.

  • Telegram keywords automatically update Jira fields
  • Urgent work gets flagged without opening Jira
  • Priority stays visible in your backlog

Setup

Build it in a few focused steps.

  • 1Ensure Telegram and Jira are connected in Notis.
  • 2Request an automation: 'When my message contains URGENT or CRITICAL, update the Jira issue priority to High'.
  • 3Notis triggers on 'New Message Received' and scans for your keywords.
  • 4Choose your notification channel for priority update confirmations.
  • 5Test by sending a message with URGENT—Notis updates the issue priority in seconds.

Questions about this workflow

Can I use multiple keywords?

Yes. You can map different keywords to different priorities—e.g., URGENT→High, CRITICAL→Highest, BACKBURNER→Low.

What other fields can I update?

Any Jira field: status, labels, custom fields, etc. Notis parses your natural language to update them.

Does it work with existing issues?

Yes. You can reference an issue by ID (e.g., 'PROJ-123: URGENT fix') and Notis updates that issue.

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 logo

Telegram triggers

Jira logo

Jira actions

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.

TriggerInstant

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

New Channel Post

Triggered when a new post is published to a channel where your bot is an administrator.

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Callback Query Received

Triggered when a user taps an inline keyboard button attached to one of your bot's messages.

TriggerInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Message Edited

Triggered when a message in a chat your bot can see is edited by its sender.

TriggerInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

New Chat Member

Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.

TriggerInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Telegram and Jira. Any combination from 985+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.