FAQ
Common questions, answered.
No. Every Jira call FlowPaths makes is read-only. It never creates, edits, or deletes issues, statuses, or workflows.
No — FlowPaths works with any Jira Software project board, whether your team runs continuous flow or sprints. It measures how work actually flowed through your statuses, which applies either way.
Issue status, type, and dates (created, resolved, updated) plus status-change history and board configuration — never assignee, reporter, comments, attachments, or any other user-identifying field. See the Privacy Policy for the full breakdown.
No. FlowPaths reads your board's existing saved filter automatically and shows a chart immediately. Setting up Status Mapping is optional but recommended, since it's what makes cycle time accurate for your specific workflow.
This is almost always a Status Mapping issue. If a status is left Unmapped, or mapped to the wrong stage, cycle time and the Dashboard KPIs will be off. Open the "Doing → Done" pill and check every status on your board is mapped correctly.
FlowPaths measures cycle time in whole calendar days by default — same-day work always reads as "1 day," whether it took 10 minutes or 20 hours. If your team's work regularly finishes within hours, try Duration mode — it switches to raw elapsed time instead, so fast items are no longer indistinguishable from each other.
Because the Doing checkboxes in the Statuses dropdown do more than filter. With some of them unticked, every time-based number becomes the time spent in the statuses still ticked, rather than the full Doing → Done cycle time — which is how you measure a single stage, like “how long does review take?”. The pill turns blue and a note above each chart says what is being measured. Tick every Doing status to go back. See Statuses dropdown.
Because WIP follows the same selection. With some Doing statuses unticked, “In progress” counts the items sitting in the statuses still ticked — so it answers “how many are in review?” rather than “how many are in progress anywhere?”. At risk and Needs attention narrow the same way, and the Forecast’s “Use current WIP” button uses the same number.
Done / total is the one that does not move, because it counts the items created in the period whatever path they took. Its own ⓘ says so while a measure is on.
No. The ticks are remembered in your own browser, per board, and are never shared or stored by the app. Status Mapping, which is shared, is unaffected. If the board’s statuses change, your view resets to the default rather than quietly measuring something you never chose.
Nowhere. The file is written by your browser straight to your own disk — nothing is uploaded, and nothing reaches us or any third party. It contains only the fields already on your screen, and no people are named in it: assignee, reporter and the authors of status changes are never included, because FlowPaths never reads them. See Export to CSV.
FlowPaths pauses and shows a “No active subscription found” screen instead of the charts. There is no countdown or trial extension beyond the one Atlassian itself provides — access resumes as soon as the subscription is active again.
Nothing is deleted. Your Status Mapping, exclusions and other settings are untouched and come straight back. If you believe you are seeing this in error, your Jira administrator can check the subscription under Settings → Apps → Manage apps; if it looks correct and the app still says otherwise, email us.
No. FlowPaths makes zero calls to any third party — no analytics, no external servers. It's eligible for Atlassian's "Runs on Atlassian" program, which specifically certifies apps with no external network egress.
Your Status Mapping and excluded-issue lists are stored in Atlassian's own Forge storage, not on any server of ours, and follow Atlassian's standard data-lifecycle/deletion process on uninstall. See Privacy Policy §7.
Yes. Status Mapping and exclusions are saved per project, so each project keeps its own configuration — switching projects in Jira automatically switches which configuration FlowPaths uses.
The board shows you what's happening right now. FlowPaths measures how work has actually moved historically, and turns that into percentiles, trend signals, and forecasts — so conversations about predictability are grounded in data instead of a felt sense of speed.
Risk is measured against your own completed cycle times, so it needs enough finished work to be meaningful. With fewer than 7 completed items the “85th percentile” would just be the slowest one you have, and with fewer than 20 the same is true of the 95th. Until then FlowPaths flags nothing and tells you how many more completed items it needs, rather than showing a number it cannot stand behind. A new project will start flagging work as soon as a handful of items finish.
They shouldn’t any more. Each issue type is judged against its own completed history once there are 7 or more finished items of that type, because Bugs and Stories genuinely flow differently. When a type has too little history of its own, risk falls back to your whole board’s history and the panel says so — an item that is genuinely running long stays flagged whichever way you filter. Note that the Cycle time (85th pct) figure is different: it always follows your filter exactly, because it describes the work you selected rather than judging it.
FlowPaths has a free tier for smaller teams, with usage-based pricing beyond that. See the Pricing tab on the Atlassian Marketplace listing for current details.
Email info@yourpaths.eu — this is also where you can report a bug or suggest an improvement.