Audit intermediate Works with: Any AI

Jira Release and Fix Version Hygiene Audit

Table output Has example

• 🧭 Jira

Check fix versions, release dates and unreleased issues in Jira for mismatches, orphaned tickets and release-note gaps before a release.

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.

Please audit the release data in my Jira project and tell me whether our fix versions can be trusted for release notes and planning. Use only what I paste. Mark any Jira-specific behaviour claims [VERIFY].

Inputs: versions with name, status, start and release dates [VERSION_LIST], issues with key, type, status, resolution and fix version [ISSUE_EXPORT], our release process in a few lines [RELEASE_PROCESS], and today's date [TODAY_DATE].

Report: (1) a version table with columns Version, Planned date, Released?, Days late or early (show arithmetic), Issue count, Done count, Open count, Flag; (2) a list of consistency problems: done issues without a fix version, issues in a released version that are still open, issues with several fix versions, versions with dates in the past that are unreleased, resolved issues marked Won't fix inside a release; (3) counts per problem; (4) a release-note readiness check: which issues have a clear summary a customer could read, which are internal in tone; (5) a clean-up plan in order, with a person role for each step; (6) a short rule set for fix versions, no more than eight rules.

Guardrails: do not move, close or release anything on your own; present proposals only. Do not guess dates. Where the export lacks a field, say what is missing.

Add a worked example with invented data: version 2.4 planned 10 March, released 17 March, containing 30 issues with 28 done and 2 open. Show 7 days late and a flag on the 2 open issues.

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.

Version table (invented)
Version 2.4: planned 10 March, released 17 March. 7 days late (17 - 10). Issues 30, done 28, open 2. Flag: 2 open issues sit inside a released version.
Version 2.5: planned 5 April, unreleased, today is 20 April. 15 days past plan. Issues 18, done 12. Flag: date in the past.
Consistency problems: 6 done issues have no fix version; 3 issues carry two fix versions.
Release-note readiness: 21 of 30 summaries read as customer-friendly = 70 percent (21 / 30).
Proposal for the team to approve: check the 2 open issues in 2.4 and move them to the next version if they did not ship [VERIFY in your Jira version]. Do not release 2.5 until the date is updated.