Features
Everything Issue Checker does, in the order you will meet it.
One headline for the whole project
One line at the top tells you how many issues need attention, how many checks found something, and what is new or fixed since you last looked. An issue caught by two checks counts once.
Every check is listed, found or not
A check that found nothing shows a green dot and a zero, so a check that found nothing and a check that never ran never look the same. Every row carries a small ?; rest on it to read what the check looks for and why it matters.
Thirty-four checks in five groups
Dependencies (5)
Work blocked by something scheduled later, already finished, in another project, or blocked in a loop; a child due after its parent.
Something missing (7)
No epic, no due date, no start date, no estimate, estimated at zero, unassigned, the same summary twice.
Dates and sprints that disagree (5)
Carried over more than once, still open in a closed sprint, waiting past its date, due outside its sprint, due before it starts.
Estimates (14)
Time logged on work not started, done with no time logged, estimates that never go down, work heading past its estimate, and how Jira settled the work.
Looks finished, is not (3)
Done with work still on it, a parent closed while its children are open, overdue.
Your own checks
Any Jira filter you write, named and counted in the headline like the rest.
Open a check to see the issues behind it
Click a row and the issues behind the count appear under it, each by key with its summary and a note saying why it was found. Click a key to open the issue in Jira. Six are listed; if there are more, the last line opens a Jira search holding all of them. A dependency loop is drawn as the loop itself, first key equal to last.
Only the checks you care about
- Choose which checks run. Untick a check and it leaves the list and every count.
- Dismiss what you have accepted. A dismissed finding comes off its check and the headline, and waits in the Dismissed list with the check that found it. Restore puts it back.
- Put them in your order. Drag checks within their group, or let the ones that found the most rise to the top.
- Show only found issues hides the quiet checks; Expand all and Collapse all open and close what is on screen.
Tell it what your columns mean
Jira sorts every status into not started, in progress or finished, and sometimes gets a column wrong: a "Ready for release" it counts as finished, a "Blocked" it counts as in progress. Say which group each column really belongs to: Not started, In progress, Waiting on something or Finished. Waiting on something is a group Jira does not have, and it is what "Waiting, and its date has passed" is built on.
Choose what to include
Every sprint the project's issues sit in is listed with a tick, closed ones included, and Include backlog adds everything not in a sprint.
Yours alone
Which checks run, their order, what each column means, what to include, your own checks and what you have dismissed are kept per person and per project, inside your own Atlassian site. Two people can look at the same project with different lists, and neither changes the other's.
Says so when Jira cannot answer
"Carried over more than once" needs each issue's history. On a large project Jira may not return all of it in time; the app then says so under the headline and counts only what it read, rather than reporting an unread issue as fine.
Reads only
It asks for no permission to write, of any kind, and sends nothing outside Atlassian. It reads issue fields and links, which sprint an issue is in and whether that sprint has closed, and the project. It does not read issue descriptions or comments.