Questions & answers
Short answers about Issue Checker for Jira. The full detail is in the Docs.
It reads a Jira project's issue fields and lists what is wrong with them: fields nobody filled in, dates that contradict each other, work blocked by something that cannot happen first, and estimates that do not add up. Thirty-four checks in five groups, plus any check you write yourself.
No. It asks for no permission to write, of any kind, and that is on the app's permission list before you install. You fix what it finds in Jira yourself.
No. It reads issue fields - summary, status, assignee, dates, estimates, time logged, resolution, sprint, parent and links - not descriptions or comments.
Inside a project, from the project's own menu, where it checks that project with nothing to set up. As a gadget on a Jira dashboard, where you choose the project in the gadget's header. Or as an app of its own, from Jira's Apps menu.
Behind the gear (⚙) at the right of the name, on a dashboard gadget and on the app's own page. They open before a project is chosen too; what you save then is where every project without choices of its own starts. The page inside a project has none of its own.
Yes. Add the gadget twice and pick a different project in each.
No. Each page or gadget checks one project.
The headline counts issues, not findings. One issue with no epic and no due date is found by two checks and is still one issue that needs attention.
That check ran and found nothing. A check that did not run never looks like one that found nothing.
It comes off its check and the headline drops by one. It waits in the Dismissed list at the top, with the check that found it, until you press Restore.
No. Your choices are kept per person and per project. Two people can look at the same project with different lists.
They say nothing on a project that does not track time, and you can switch them off so they leave the list.
Yes. In the settings you can say, column by column, whether a status is not started, in progress, waiting on something or finished. Your word wins over Jira's.
Yes. Give it a name and a Jira filter written the way you would in Jira's search box. Test tells you whether Jira accepts the filter and how many issues match right now.
No. Your choices are kept inside your own Atlassian site, and the app sends nothing anywhere else.
It is a separate app from the same maker. Nine of its checks are the same checks Project Commander's Alerts tab runs, asked of the same engine, so the two never give different accounts of one project. Project Commander goes on to say whether the plan fits the capacity your team has.