Field value duration for BI purpose

Hi everyone,

Thanks for your answers! It's good to know that add-ons exist just for that, I'll try to review them but in any case I'm confident that my requirements can be met without changing my architecture!

For those who can't rely on add-ons, I have built something based on native features. Basically:

1. Build 2 types of SLAs: time for resolution and time to assign; you want them to reset when a Team is changed (in my case)

2. Each time a SLA is reseted, add a worklog with the SLA duration; the description of the worklog will contain the type of SLA and the team involved

3. The BI only needs to get the worklogs and read them

Cheers,

Simon

Hi!

Alexandre Pezzini, thanks for recommending Issue History for Jira (SaaSJet). 

slucchesini, really, the app provides Field changes duration report that automatically calculates the time difference between the selected field changes available when downloading reports using the Excel (Advanced) export. Here is an example: 

Also, the app has Time in field values report that shows how long work items stayed in each field value. An example of the report: 

Also, the Issue History for Jira app provides an API that can be used to automatically export complete Jira work item history to various BI tools. More info can be found here: Jira API for History Export

In addition to Issue History for Jira, you may also consider SLA Time and Report for Jira by SaaSJet if you need to track this time against specific service targets.

For example, you can configure an SLA to run while the Team field has a particular value and stop or restart when the team changes. With multi-cycle tracking, the app can also calculate the total time spent by the same team if the issue is assigned to it more than once.

Beyond time tracking, the app allows you to set SLA goals, apply working calendars, monitor remaining time directly in Jira issues, receive alerts before a breach, and analyze results through reports, dashboard gadgets, and exports.

Hi, @slucchesini 

Just to add another option — eazyBI for Jira can handle this use case natively without requiring heavy API scripting on your side.

eazyBI imports Jira issue changelog data during its regular import process. Using JavaScript calculated custom fields, you can track how long any custom field (such as your "Team" field) held each value, and import those durations directly into eazyBI as measures. From there, you can build reports showing time per team, per issue, per time period, and much more — all without probing Jira's API at query time.

Hope this helps as an alternative worth considering!

Kindly,

Ilze

Hey @slucchesini

As Alexandre mentioned, there is indeed a magical "Field value duration" add-on, so you do not need to change your flexible architecture or build heavy API scripts to parse issue histories!

You can easily track these exact metrics using Timepiece - Time in Status for Jira.

Here is how you can get your team stats effortlessly:

Use the Any Field Duration Report: This advanced report type is designed exactly for this use case, allowing you to see how long any specific issue field held each value without needing to map them to statuses.

Select your 'Team' field: By selecting your "Team" field as the history field, the report will list your tickets in rows and dynamically create columns for each team value (Support N1, N2, etc.), showing the exact time the ticket spent with each team.

Easy BI Integration: If you still want to bring this data into your BI app, Timepiece has an extensive REST API that provides these pre-calculated reports directly as JSON or CSV files.

This saves your system from the heavy lifting of probing raw Jira changelogs.

To learn more, you can find Timepiece - Time in Status for Jira on the Atlassian Marketplace.
Full disclosure, I'm on the team that makes Timepiece. Hope this helps!

Best,
Birkan