You can build this with native automation, but as @Bill Sheboy hinted, you'll need one custom field per status you want to measure plus a small set of rules. Here's a working pattern for one status - repeat it for each status you care about.
One-time setup (per status, e.g., "In Progress"):
In Progress - Entered At, and a number field In Progress – Hours.Rule 1 — capture the entry timestamp:
In Progress – Entered At = {{now}}Rule 2 — capture the exit and add to the running total:
In Progress – Entered At is not emptyIn Progress – Hours = {{#=}}{{issue.In Progress – Hours}} + {{now.diff(issue.In Progress – Entered At).hours}}{{/}}In Progress – Entered At = (clear)The {{#=}}…{{/}} expression is Jira's mathematical-expression smart value — it adds the just-elapsed duration to whatever was already in the total. Each round trip through the status accumulates correctly.
A few caveats worth knowing up front:
if checks against now.dayOfWeek).For dashboard reporting, once the - Hours fields are populated you can use Two-Dimensional Filter Statistics with Assignee × In Progress – Hours (Statistic Type), or chart them in any list/issue navigator with the field as a column.
Hope this helps,
Ivan
@Anser Ghazzaal AliFollowing up on my earlier answer - I know you specifically asked for the native automation route, and that's above. Just flagging one more option in case the rule sprawl ends up being more maintenance than the data is worth.
If you're open to solutions from the Atlassian Marketplace, JXL reads time-in-status directly from the work-item changelog Jira already keeps. You add a "Time in " smart column for any status, and the values populate retroactively for every existing issue with no fields, no rules, and no backfill scripts. You can group by assignee or sum across multiple statuses for cycle-time-style metrics.
Disclosure: I work for the team that builds JXL. Sharing this as an option, not a sales pitch - the native automation pattern works fine if you're set on it.
Cheers,
Ivan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Anser Ghazzaal Ali
Calculating time spent across multiple statuses and triggering actions based on that data isn't possible with native Jira automation alone, but it becomes straightforward with Timepiece - Time in Status for Jira.
If you are open to using a Marketplace app, you can achieve this using Timepiece's Duration Between Statuses report combined with Jira Automation. This report type lets you define a metric that measures the total time an issue spent traveling through multiple statuses — for example, from "In Progress" to "Resolved" — and then use that data directly inside your automation flow to post comments, update fields, or trigger transitions.
1. First, you need to create a Cycle Time metric within the app.
2. In the report, you will see the calculated results based on the statuses you selected for that metric.
3. Create an automation and add Timepiece to the automation.
4. The automation will run when the defined conditions are met and will post a comment, just like in the example I showed.
You can find detailed instructions on how to create an automation in Atlassian's Getting Started with Jira Automation article.
Additionally, you can access our documentation, which includes a comprehensive collection of automation use cases and guides.
You can find Timepiece - Time in Status for Jira on the Atlassian Marketplace. After installation, reports can be generated instantly based on your existing issue history.
Full disclosure, I'm on the team that makes Timepiece. Hope this helps!
Best Regards,
Melisa Mutlu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Short answer: Would you please explain what outcome you are trying to achieve with these measures? What would your team do differently if you had that information right now? Knowing those answers will help the community provide better suggestions.
Until we know that...
Other than for a very simple workflow (e.g., Todo, In Progress, and Done), measuring time-in-status with automation rules can be challenging. This why marketplace vendors are suggesting products to you: their products can get the data from the work item changelog / history and process it with app code more easily than a rule or built-in Jira features can.
How do you want the time measures provided: a chart, number values, etc.?
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Bill, for your effort.
But it looks like every answer is trying to push me towards buying third-party solutions, why Atlassian did not develop this small and important feature in Jira. Maybe they also try to push clients to buy third-party solutions.
I need only the time spent by one work item in one status, where Jira is already storing the incoming and outgoing time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please re-read my post where two built-in approaches are noted: the Control Chart and building automation rules.
What happened when you tried those approaches? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Anser Ghazzaal Ali
I you need to get the time each work item remains in each status you can use the SLA report of the Gadget Utilities for Jira Cloud
You can select the filter of work items to display and add the statuses you can track
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I need an automation step-by-step workaround, not marketing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Anser Ghazzaal Ali ! You can actually handle this with our app Time Metrics Tracker | Time Between Statuses
It lets you calculate time spent in any status or between multiple statuses, and you can fully customize the metrics to match your workflow (cycle time, waiting time, time between specific steps — whatever you need).
On top of that, you get solid visualization tools like scatter plots, WIP charts, and trend gadgets to really understand what’s going on in your process — plus alerting if things start taking too long.
Also, it includes Manage Work Schedule, so your calculations can take into account working hours, weekends, and holidays, which makes a big difference if you want accurate numbers.
Happy to share more details if you’re exploring options 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I need an automation step-by-step workaround, not marketing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.