/
/
Understand where a Jira issue stands and what blocks it
For developers and leads who want an issue's full story in one read instead of every tab, by asking their AI assistant.
On this page
Connector
Connect Jira, pick your AI tool and paste the prompt.
The problem
Working out why an issue is stuck means clicking every tab
Understanding why a Jira issue is stuck means reading its detail, scrolling comments, checking time logged, opening subtasks and following links. It is slow enough that people ask in chat instead and get half the story.
Without PopdockAI
- Read the issue detail and people
- Scroll through the comments
- Open subtasks and logged time
- Follow links out to other systems
With PopdockAI
- Status, people, dates and recent comments are gathered
- Time logged, subtasks, attachments and links are added
- The last five comments are quoted in order
- What appears to block it is stated, and nothing is changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Assemble everything known about the Jira issue `{issue-key}` and explain its current state, who is involved and what is blocking it.
**Step 1: Get the issue**
Call `jira-get-issue` with issue-key set to {issue-key}. If it returns nothing, say the issue was not found and stop. Keep project-key, status, assignee, reporter, created-date, updated-date and due-date.
**Step 2: Resolve the numeric issue id**
The issue list does not carry the numeric id that the detail lists filter on. Call `jira-get-issue-watcher` with issue-key set to {issue-key} and read issue-id from the result. If it returns no rows, note that the numeric id could not be resolved and continue with Step 5 only.
**Step 3: Activity**
Using the issue id from Step 2:
* `jira-get-issue-comment` with issue-id set to that id, to get the conversation in date order
* `jira-get-issue-worklog` with issue-id set to that id, for who has spent time and how much
**Step 4: Structure and context**
* `jira-get-issue-subtask` with outward-issue-key set to {issue-key}, for child work and its status
* `jira-get-issue-attachment` for files, and `jira-get-issue-remote-link` for links out to other systems
* `jira-get-issue-watcher` from Step 2 also tells you who is following the issue
**Step 5: Report**
* one paragraph on where the issue stands and whether it is moving
* a short timeline of the last five comments: date, author-name, one line of the body
* time logged: total time-spent and the authors, or "none logged"
* subtasks: key and status each, and whether any are incomplete
* links and attachments: names only
* a closing line naming what appears to be blocking it, or saying nothing obvious is
**Rules & Guidelines:**
* Read only. Do NOT call `jira-add-issue-comment`, `jira-update-issue`, `jira-update-issue-comment`, `jira-assign-issue`, `jira-add-issue-worklog`, `jira-add-issue-vote`, `jira-add-issue-watcher` or `jira-add-issue-remote-link`.
* Quote comment bodies, do not paraphrase them into conclusions they do not support.
* Say explicitly when a detail list returns nothing, rather than leaving it out.
**Validation:**
* If {issue-key} is not a single key, ask for one and stop.
* If Step 2 cannot resolve the id, report the issue detail and the subtasks, and say the comments and worklogs could not be read because the issue has no watchers to resolve its id.Who it's for
One answer, three teams that use it
Developers
Pick up an issue with full context
Get the history, subtasks and links of an issue you inherited before you start work.
What is going on with API-219 in Jira? Summarise it and what is blocking it.
Engineering managers
Understand a stuck issue fast
See what is holding an issue up without asking in chat or reading every comment.
Why has MOB-88 been in progress for three weeks?
Project managers
Prepare a status answer
Get time logged and recent comments, quoted rather than stretched, for an accurate update.
Give me the current state of WEB-1107, including time logged and open subtasks.
How it works
What PopdockAI does when you ask
You name the issue and your AI assistant gathers everything Jira holds on it. You get a summary and what appears to block it, and nothing is changed.
01
Ask
You name the issue.
02
Read
It gathers status, people, dates and recent comments.
03
Gather
It adds time logged, subtasks, attachments and links to other systems.
04
Report
You get a summary, the last five comments and what appears to block it.
What PopdockAI provides
The tools behind the answer
Ready made tools for Jira and one secure connection to your AI tool. No code, no exports.
jira-get-issue
jira-get-issue-watcher
jira-get-issue-comment
jira-get-issue-worklog
jira-get-issue-subtask
jira-get-issue-attachment
jira-get-issue-remote-link
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Where any issue stands, in one read
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
