Backlog Age and Stale Issue Audit
Find old, duplicated or unclear backlog issues and decide what to close.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit my Jira backlog for staleness. An export or list of issues with key, type, summary, created date, last updated date, priority, labels, assignee and status: [BACKLOG_EXPORT]. Today's date: [TODAY_DATE]. What the team can realistically do in the next two quarters: [CAPACITY]. Calculate the age of each issue in days (today minus created) and days since last update, show the arithmetic for a sample, and group issues into age bands (under 30 days, 30 to 90, 90 to 180, over 180). Count the share in each band. Identify likely duplicates by similar summaries, vague issues with no description, issues with no owner, and issues whose priority conflicts with their age. Propose a close, merge, rewrite, or keep decision for each group with a reason, and draft a closing comment of under 40 words that is polite and explains how to reopen. Add a rule to prevent repeat buildup (monthly grooming, maximum backlog size) and a communication note to stakeholders before closing items. Do not close anything automatically; present decisions for a person to approve. Mark Jira-specific bulk actions as [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.