Separating Casual Telegram Conversations from Jira Tasks

Separating Casual Telegram Conversations from Jira Tasks

2 min read 15 views
We’re building a solution for a client that distinguishes casual Telegram messages from genuine work requests. This reduces the number of incorrect tasks created on the Jira board.

The client’s team communicates in Telegram groups and tracks work requests through Jira. The assistant treated some casual messages that mentioned people as work requests and created incorrect tasks on the Jira board. Team members then had to find, review, and delete those entries.

We’re adjusting the assistant so it can distinguish casual conversation from genuine assignments more accurately. Group members can mention one another and chat freely, while only work requests that require action are added to the Jira board.

Not Every Mention Is a Work Assignment

Mentioning someone in a group can mean different things. Someone may be waiting for a reply, sharing information, or directing the conversation to that person. The previous setup treated some of these messages as tasks too.

One incorrect task may seem like a minor issue. But someone still has to find it on the Jira board, confirm that it is not actually an assignment, and delete it. As these errors add up, trust in the board begins to decline.

Casual Conversation Stays in the Chat

We’re changing the assistant’s message-selection rules. A message marked as not being a task stays in the conversation. Genuine requests phrased politely, as well as assignments that include an image or file, should still become Jira tasks.

The solution should not simply reduce the number of tasks. It needs to move genuine work requests to the Jira board while leaving casual communication where it belongs.

A phone shows several chat mentions with only one marked as a work request
Not every group mention is a work assignment.

How a Message Moves from the Group to the Jira Board

  1. A Message Is Posted A group member mentions another person in the conversation or addresses them directly.
  2. The Message’s Purpose Is Identified The assistant determines whether it is casual conversation or a work request that requires action.
  3. The Right Task Is Created Only messages identified as genuine work requests are added to the Jira board.

The Manager Sees All Relevant Tasks in One Document

The project also includes a separate document for the manager. It will bring together all relevant tasks, their full descriptions, and links. Instead of reviewing the Jira board page by page, the manager can read the necessary information in a single document.

The document will initially be provided privately to one user. The rest of the team will continue using the existing buttons on the Jira board. The project is still in progress, with approximately 24 hours of engineering work allocated to it.

A message route runs from a phone through an intent check to a kanban task card
Route: group message, intent check, Jira card.

Three Lessons for Similar Teams

  • A Mention Does Not Mean an Assignment. Task creation should be based on whether the message contains work that needs to be done, not simply on whether someone was mentioned.
  • Make the Exclusion Marker Clear. Clearly marking messages that are not tasks reduces the number of incorrect entries created on the Jira board.
  • Don’t Change the Team’s Habits Overnight. A new view can be introduced to selected users first while the rest of the team keeps its existing workflow.

Let Only Work Requests Move from Telegram to Jira

If you need to convert Telegram messages into Jira tasks more accurately or adapt your task board to your team, contact Celion. We’ll first identify where messages are being misinterpreted, then plan a solution that fits your workflow.

Contact us

Share this article