I need to track time in between the fields

[Giridhar Ujjinappagari]

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

[Rahul_RVS]

Hi @Giridhar Ujjinappagari 

Welcome to the community !!

You can use Jira Rest API's to extract the historical data or if you would be interested in a mktplace app for this requirement, you can try out

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options.

The app also has "Time in Field" report which can help the total time your issues spend in a particular field value.

Also the app has 20+ reports to meet a variety of use cases.

More details here.

Disclaimer : I am part of the app team for this add-on

[Birkan Yildiz _OBSS_]

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.

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.

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.

[Petru Simion _Simitech Ltd__]

Hi @Giridhar Ujjinappagari , 

You can write a scripted field that can derrive the time between statuses.

It will be some extensive work.

If you are open to using apps, you can use Time in Status Reporter for Jira an app released by our company.

You will be able to see how long the issue spent in each status and according to your workflow this will answer your question.

Regards, 

Petru

[Tomislav Tobijas]

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]

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,

Thanks,

Giridhar U.

[Tomislav Tobijas]

Ah, thanks for clarifying @Giridhar Ujjinappagari 

MTT* fields are clear, and what about those values for 'Start Date and Time,' 'Detection Date and Time,' etc.? Do these values exist on old items, or are these also empty?

If they are, it would really depend on the process itself (how and when you're populating these fields). 

Automation does support smart values such as:

• {{issue.created}}
• {{issue.resolved}}

Which would return exact timestamps of when the work item was created and when the resolution was (last) set.

As you'll likely see, numerous Marketplace apps focus on reports from work item history, which may be helpful.
What I know my colleagues do when we have requirements similar to this one, is build up a script (Groovy or Python) and then extract all historic data from required work items. Then we parse those results and re-import/add them to existing items.