Quick answers
Frequently asked questions
Open only the answer you need. For setup values tied to a real delivery problem, use the practical playbooks.
I finished setup, but the queue is empty
Check View Flow Guard queue under Settings → System → Global permissions first. It ships granted only to Jira administrators. Then confirm monitoring is active, Last complete scan has a timestamp, and no queue filter remains. An empty queue can also be correct when no issue crosses a configured threshold.
There are too many findings
Set a status-specific aging threshold first—for example, Review at 24 hours while the fallback remains 72. Then use dismiss reasons accurately: a high share of Expected workflow means that status needs a longer threshold or exclusion. Narrow project scope last.
There are too few findings
Check the business calendar. At 8 hours/day and 5 days/week, a 72-business-hour threshold is about 9 calendar days. Done-category statuses are excluded, and a near release does not add a healthy issue by itself.
What does the score mean?
It is a rule-based intervention order, not a probability of delay. The 100 points are split across flow delay (40), delivery impact (30), coordination (15), and corroboration (15). The finding detail shows every observed value, threshold, and contribution.
Why do I see Estimated or Install baseline?
Jira does not always expose the exact time of every status transition. Estimated uses a lower-fidelity Jira timestamp; Install baseline means the duration is measurable only since installation. Precision improves as Flow Guard observes changes.
What is the difference between snooze and dismiss?
Snooze returns after 1, 3, or 7 days, or on a chosen date at 09:00 in the site time zone. Dismiss hides a finding for 30 days but returns earlier after a material issue change. Dismiss requires a reason for weekly review feedback.
Is bulk triage safe?
It applies only to issue versions listed in the confirmation. Anything changed after confirmation or no longer visible to you is excluded and returned for individual review.
Where is data stored?
Stored app data remains in Forge storage on Atlassian infrastructure. Flow Guard does not store issue summaries, display names, account IDs, or comment bodies. Visible issue details are fetched from Jira under the viewer’s permissions. Administrators can export or delete app data from Privacy and data.
Does Flow Guard send notifications automatically?
No. Daily and weekly digests are off by default. Each user opts in for themselves, and Jira permissions are checked again for every delivery.
Is Japanese supported?
Yes. The app follows each viewer’s Jira language setting for English or Japanese. This help center is also bilingual. The canonical Marketplace listing remains a single English listing.