<aside>
💡
What is CyclePulse? A Jira Cloud app that shows how long issues spent in each workflow status, and with each assignee, on your real working hours. It adds Lead Time, Cycle Time and Flow Efficiency, a trend chart, Lead and Cycle Time as Jira fields, and CSV and Excel export.
</aside>
Who is this for
- Team leads, Scrum Masters, and managers reviewing flow and bottlenecks
- Support and ops teams measuring SLA time in status
- Anyone who needs a Jira status-time report without leaving Jira
Where to find it
- Open Jira Cloud
- Go to Apps > CyclePulse: Issue Time in Status & Exports in the top navigation
- The report page loads with your first project pre-selected and last 30 days of created issues
You need Browse Projects permission for the projects you want to analyze. If a project is missing from the dropdown, ask your Jira admin for access.
What you see on first load
- Filter section at top with two tabs: Basic and Advanced JQL
- Summary cards: total issues, average Lead Time and Cycle Time with median and P85, Flow Efficiency, status transitions
- Insights: status breakdown, time per assignee and a trend chart
- Report table: one row per issue, with columns per status
- Table controls: columns, status groups, Time or Visits, duration format
- Export: CSV and Excel, for preview or full results. Your Jira admin can limit who sees it
Privacy note
CyclePulse runs entirely on Atlassian and makes no external network calls. Reports are calculated in your browser with your own Jira permissions, and interrupted large exports are stored only in your browser's IndexedDB so you can resume them. If a Jira admin switches on the Lead Time and Cycle Time Jira fields, the app also reads issue history in the background on Atlassian's Forge platform to keep those fields up to date.
For Jira administrators