Statusdesk for Jira
How long work sits in each status — on the issue, in working hours, and in JQL.
An Atlassian Forge app by DataForte AB, available on the Atlassian Marketplace.
What it does
- Shows the time an issue spent in every status it has been through, and how often it came back to each one.
- Counts working time instead of wall-clock time. A ticket raised on Friday at 16:00 and picked up on Monday at 10:00 is 2 hours of working time, not 66.
- Writes days in current status, cycle time and a short status summary into Jira fields you own, so the numbers work in JQL, filters, boards, dashboards and automation instead of living inside a panel.
- Reports lead time (created → done) and cycle time (first move → done), and flags an issue that was reopened after being closed.
- Refreshes untouched open issues daily, because “stuck for six days” is a number that grows without anything happening on the issue.
Setup
- Create three custom fields in Jira — Settings → Issues → Custom fields: a number field for days in current status, a number field for cycle time, and a short text field for the status summary.
- Add them to your project. Company-managed projects: put them on the issue screens. Team-managed projects: Space settings → Fields → Add field.
- Open the Statusdesk admin page, paste the three field ids, and turn working hours on.
How your data is handled
Statusdesk runs entirely on Atlassian Forge. There are no servers of ours, and the app makes no external calls at all — every number is computed from the issue changelog Jira already stores, inside your own Atlassian site.