Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I need to track time in between the fields

Giridhar Ujjinappagari
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 18, 2025

I need to track time in between the fields , I have created automation ,here I can able to track the time in between the fields for newly created issues only.But I want to track the time for old issues also 

How it will be done can anyone explain

2 answers

0 votes
Birkan Yildiz _OBSS_
Atlassian Partner
December 19, 2025

Hey @Giridhar Ujjinappagari

Welcome to the Community!

That's the biggest challenge with Jira Automation. It's great for new triggers, but it can't look back at your old issues to calculate durations retroactively.

Timepiece - Time in Status for Jira has a report that solves this using your existing issue history.

It’s called the Any Field Duration report.

Instead of relying on automation, this report allows you to see exactly how long a specific field held each value. This effectively tracks the "time in between" any custom or system field changes.

Screenshot 2025-12-19 110851.png

For example, if you use a custom field (like priority) to track a specific state or "wait time" without using a workflow status, this report will calculate exactly how long that field spent on each value.

Screenshot 2025-12-19 113212.png

The best part is that because it reads from your issue history, it works for all your old issues immediately, giving you the data you need without any new automation rules.

You can check Timepiece on the Atlassian Marketplace. Hope this helps you get the tracking you need!


Full disclosure, I'm on the team that makes Timepiece - Time in Status for Jira.

0 votes
Tomislav Tobijas
Community Champion
December 19, 2025

Hi @Giridhar Ujjinappagari ,

Are you looking to track differences for transitioning a work item to another status, or are you monitoring some other field? 👀

As you've noticed, once you build an automation, it will work for new items, but related to previous ones, you would need a logic that would look at those entities retrospectively. 
For pretty much any use case here, if you would like to get historic data for an item, you would need to check the work item history.

Now, whether you could use this in automation directly, or would it be maybe easier to get all changelogs locally, parse the data, and then 'upload' those values/info to existing items... that's something that needs additional testing.

Anyway, to get work item history, you could use Get changelogs REST API 👈, which should then return all changes on a particular item. From the given response, you could parse when a specific value was changed, and then you could populate that new field you have for tracking the difference. 

Again, this might require some work. It also depends on how far in the past we're looking at, and how many items you have that need to be updated.

Cheers,
Tobi

Giridhar Ujjinappagari
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 19, 2025

Hello Tomislav Tobijas

 

I need to track time in between two fields not statuses,

Incident start date and time to incident detection date and time time will be tracked in MTTD(mean time to detect) like wise i need time tracking for old issues.

Can you please check the screenshot,

Screenshot 2025-12-19 at 1.51.10 PM.png

 

Thanks,

Giridhar U.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events