/
/
Start each sprint with a ranked Jira shortlist
For project managers who want the backlog ranked on due dates, ownership and staleness, by asking their AI assistant.
On this page
Connector
Connect Jira, pick your AI tool and paste the prompt.
The problem
A long backlog hides what to pick up next
A long Jira backlog makes it hard to see what to pick up next: overdue items sit next to old ideas, and unassigned urgent work hides among stale tickets. Sorting it by hand every sprint takes time the team does not have.
Without PopdockAI
- Scroll the whole backlog
- Sort by due date, then by age
- Spot unassigned urgent work by eye
- Debate priorities in planning
With PopdockAI
- Open issues are ranked on due dates, ownership, age, staleness and size
- Past due work comes first, then live unassigned work
- Up to 20 issues with the top three and reasons
- It says when data is thin, 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:** Triage the backlog of the Jira project `{project-name}` and recommend, in order, the issues that should be worked next. Consider issues updated in the last `{lookback-days}` days (default 30) as active.
**Step 1: Identify the project**
Call `jira-get-project` with name.contains set to {project-name}. If more than one project matches, list the matches with their project-key and number-of-issues and stop. If none match, try project-key set to {project-name}. If that is also empty, say so and stop.
**Step 2: Pull the issues**
Call `jira-get-issue` with project-key set to the key found in Step 1 and max-records set to 200. If {status} is supplied, pass it as status; otherwise pull everything and exclude anything whose status reads as Done, Closed, Resolved or Cancelled.
**Step 3: Rank**
Score each remaining issue on:
* age: created-date far in the past with no recent updated-date
* staleness: updated-date older than the lookback window
* ownership: assignee empty is a risk, not a reason to skip
* size: story-points where present
* commitment: due-date already passed, or falling inside the window
Put anything past its due-date first, then unassigned work that is not stale, then the oldest stale items.
**Step 4: Report**
A table of at most 20 rows: issue-key, summary, status, issue-type, assignee, due-date, days since updated-date. Below it, three to five sentences naming the top three to pick up and why, and one line on anything unassigned that looks urgent.
**Rules & Guidelines:**
* Read only. Do NOT call `jira-add-issue`, `jira-update-issue`, `jira-assign-issue`, `jira-add-issue-comment`, `jira-add-issue-worklog`, `jira-add-issue-vote`, `jira-add-issue-watcher`, `jira-add-issue-remote-link`, `jira-update-issue-comment`, `jira-add-project` or `jira-update-project`.
* Rank on what the issue rows actually contain. Do not guess at priority, there is no priority field on the issue list.
* Say when the data is thin rather than inventing a justification.
**Validation:**
* If Step 2 returns nothing, report that the project has no issues matching the filter and stop.
* If {project-name} matches several projects, stop at Step 1 and ask which one.Who it's for
One answer, three teams that use it
Product owners
Walk into planning with a shortlist
Start sprint planning with the top issues and the reasons they matter.
Triage the MOB backlog in Jira. What should we take into the next sprint?
Scrum masters
Surface urgent unassigned work
Unassigned issues that look urgent are called out, so they do not hide in the backlog.
What unassigned work in the API backlog looks urgent?
Engineering managers
Focus on what is past due
Past due issues rank first, with the oldest stale items after them.
Rank the open issues in WEB with status To Do and tell me the top three.
How it works
What PopdockAI does when you ask
You name the project and your AI assistant ranks its open issues. You get a shortlist with reasons, and nothing in Jira is changed.
01
Ask
You name the project and optionally a status and activity window.
02
Read
It reads the open issues in the project.
03
Rank
It ranks them on due dates, ownership, age, staleness and size.
04
Report
You get up to 20 issues and the top three with reasons, changing nothing.
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-project
jira-get-issue
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
A ranked shortlist for every sprint
Related use cases
More ways to put this data to work
Backfill Jira issues for untracked errors
Ask your AI to backfill Jira issues for untracked Bugsnag errors and it drops errors already tracked, then creates and links capped issues after you approve.
Learn More
Create a Jira issue
Ask your AI to create a Jira issue and it resolves the project, issue type and assignee before writing, then creates it once after you confirm.
Learn More
Track an error as a Jira issue
Ask your AI to track a Bugsnag error as a Jira issue and it checks for an existing issue, creates one after you approve, adds the detail and links both ways.
Learn More
Audit stale Jira issues
Ask your AI to audit stale Jira issues and it sorts open work into untouched, unassigned, past due and unestimated groups, then names the one action that clears most.
Learn More
Jira project activity report
Ask your AI for a Jira project activity report and it counts work raised, moved and completed in a date range and says whether intake is outpacing delivery.
Learn More
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.