How to calculate how much time each filed value was selected whithin a ticket.

[Édpo César]

I need to calculate how much time each filed value was selected whithin a ticket.

For example, in the field "Team", there are three possible values: 1, 2 ,3.

During the resolution process, every team may be involved in hadling the ticket, each whitin its own time frame.

I would like to know, how much time was spent under each value filed of the "Team", so we can calculate the action time for each team.

There is a feature request for that using SLA:
https://jira.atlassian.com/browse/JSDCLOUD-2297

Hey guys, I'm just brainstorming — ran out of ideas over here. 😅

[Birkan Yildiz _OBSS_]

Hello @Édpo César

Calculating the time a ticket spends assigned to each value of a custom field is a key reporting requirement for measuring team performance. 

Jira's native reports can show a field's current value, but are not designed to calculate the total time an issue has spent with each previous value. A specialized app is needed to get these duration metrics.

My team at OBSS created Timepiece - Time in Status for Jira to solve this exact problem. You can achieve this using our Any Field Duration report.

This feature allows you to select your "Team" custom field and automatically calculates the total time issues have spent assigned to each respective team.

The report presents this data clearly, giving you the precise action time for each team. One of the key metrics this report provides is:

Total Time: This shows the cumulative duration for which an issue was assigned a specific field value. It answers the exact question, "How much time was the ticket handled by Team 1?''

So, you can turn complex historical data into an actionable report without any manual work. Timepiece - Time in Status for Jira reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts. And the app has a REST API so you can get the reports from Jira UI or via REST API. Also you can export the reports in to various formats easily. 

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process.

Disclosure: I work for OBSS, the creators of Timepiece - Time in Status for Jira. Please let me know if you have any other question.

[Édpo César]

Thanks, @Birkan Yildiz _OBSS_.

This is exactly want I wanted!

[Birkan Yildiz _OBSS_]

Happy to hear that @Édpo César 

Please let me know if you have further questions. 

[Rahul_RVS]

Hi @Édpo César 

If you would be interested in a mktplace app, you can try out

Time in Status Reports 

The "Time in Field" report will help to calculate the time the issues spend in each field. Also the app has 20+ reports to meet a variety of use cases.

The example below shows the time the issue spends with each Team which is a custom field.

More details here.

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

[Valeriia_Havrylenko_SaaSJet]

Hi @Édpo César 👋

Out of the box, Jira doesn’t provide this level of detail. SLA timers only cover status-based time tracking (and the feature request you linked is still open).

However, here are a couple of approaches you can consider:

1. Marketplace Apps

Tools like Time Metrics Tracker | Time Between Statuses (developed by my team) can help here. While Jira natively tracks time in statuses, Time Metrics Tracker lets you create custom time metrics based not only on statuses but also on transitions tied to field changes.

• You can set the metric to start when the field changes to “1” and stop when it changes to something else.

• Reports can then show you exactly how much time each team handled the ticket, including averages across issues.

• Plus, you can view it in Agile Metrics gadgets, Scatter Plot, or Histogram directly on your Jira Dashboard.

2. SLA Workarounds

If your teams manage issues through specific statuses (like “In Team 1 Review”), you could configure SLAs per status in Jira Service Management. This doesn’t cover field values directly but may provide a close approximation if your workflow mirrors team handoffs.

3. Automation + Custom Reporting

With Jira Automation, you could log timestamps when the Team field changes and calculate differences via a custom field or external reporting tool (BI integrations). This requires more setup and often some scripting.

[Petru Simion _Simitech Ltd__]

Hi @Édpo César ,

You can create a scripted field that parses the issue history and calculates the diffs.

Alternativelly, if you are open to using apps, you can use Issue History Dashboard for Jira (Work Item History) , an app released by our company.

You can filter by Field Updated = [Your field] then order the columns by issue key.

The change datetime is present in column Date of Change.

You can export to CSV and write a formula in Excel to calculate your diffs.

Regards, 

Petru

[Lucas Modzelewski _Lumo_]

So basically you need a custom SLA counted from time when Team field changes. 

It can get tricky - especially since Jira SLAs are built around status changes, not field changes.

A more Jira-native workaround is to:

• Create custom statuses like:

  • Waiting for QA

  • Waiting for Dev

  • In QA

  • In Development

• Update your workflows to include transitions to these statuses when the team changes.

• Then, define SLAs based on time spent in these statuses - Jira Service Management supports this out of the box.

You don’t even have to expose those statuses to customers (in portal view) - they can be internal statuses used only for SLA tracking and internal workflows.

This approach keeps your SLA tracking transparent, reportable, and consistent - without needing scripts or automation to track custom field history.