Why teams use Task Flow Simulator
What‑If & Monte Carlo
Adjust capacity %, defect ×, inflow/week. Get completion dates with P50/P85/P95, histogram and CDF.
Data Quality Index
Checks weeks(n), min/median/mean/max, CV. Warns when history is too short or unstable.
JQL‑aware & Safe
Source by JQL / Project / Epic keys. Time‑bounded queries to avoid unbounded scans.
Configure (Edit screen)
Source
- Mode: JQL / Project / Epic keys
- History window: weeks for learning throughput (e.g., 8–26w)
- Scope policy: All open / Updated in last N weeks
- Include zero weeks: count silent weeks for realism
Simulation
- Method: Throughput Monte Carlo (Cycle‑time model coming)
- Runs: 500–10,000
- Defaults: Capacity %, Defect ×, Inflow/week
Analysis modules
How it works
History & Scope
History JQL collects issues with resolutiondate in the window (weekly throughput). Scope JQL counts open items to finish.
History example: status=done AND resolutiondate >= startOfDay(-13w) AND issuetype=Bug
Simulation
Monte Carlo draws weekly throughput samples and applies capacity %, defect ×, inflow. Output → weeks‑to‑done and P‑dates.
Outputs: P50 / P85 / P95 dates Histogram & CDF Burn‑up confidence bands
FAQ
Why is histogram diagonal?
If weekly throughput has a narrow distribution (e.g., ~7 every week), samples cluster tightly, so bars step diagonally.
How reliable are forecasts?
Check the Data Quality Index. More weeks and lower CV → more reliable. Use Control Charts to spot shifts.
Support
Contact your app admin or the development team. Please include:
- Screenshot + Jira URL (redact sensitive info if needed)
- History/Scope JQL and module used
- Browser & OS; dev tunnel or production