Hi Sirs,
I wanted to share a workflow I built for my engineering team to solve the eternal "Jira Hygiene" problem.
The Problem:
My developers often forget to update ticket statuses after the Daily Standup. The information is shared verbally ("I fixed the API bug," "I'm blocked on tickets X"), but it rarely makes it to the board.
The Solution:
I built an integration that listens to the standup audio and uses the Jira Cloud REST API to update the tickets automatically.
How it works technically:
Ingest: Captures audio from the meeting.
Context Mapping: An LLM analyzes the transcript and maps the intent to specific Issue Keys (e.g., PROJ-123) assigned to that user.
API Call: It constructs a payload to update the transition ID (e.g., moving to "Done") or addComment.
Human Loop: I added a UI layer to approve the API calls before they are sent, to prevent hallucinations.
The Result (30s Demo):
https://www.youtube.com/watch?v=XMHncCgrLzE
I'm currently running this with my internal team.
I’m curious if other Jira Admins have experimented with "Voice-driven" workflows? Any edge cases with the API permissions I should watch out for?
Thanks,
Mantas
Community moderators have prevented the ability to post new answers.
Hi @Lendor Lnd, when you're part of an Atlassian Partner team, we kindly ask that you also include text in your comment stating you work for the company that built the app, per our Partner Rules of Engagement. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.