Time in status not working properly

[Yves Defossez]

When I extract the "time in status" via a google sheets addon it gives the following string:

10180_*:*_1_*:*_30579_*|*_10182_*:*_1_*:*_10061

I know the first value is the id of the status, the second is the amount of times it has been in this status and the third value is the time itself.

All goes well but for some reason, 1 status is always skipped even though the issues must pass this status according to the workflow.

Anyone with an idea why this is happening?

[Petru Simion _Simitech Ltd__]

@Yves Defossez , 

To determine the exact time an issue spent in a specific status, you'll need to analyze the issue history and manually calculate the duration. This involves:

- Identifying the timestamp when the issue transitioned into the specified status
- Identifying the timestamp when the issue moved out of that status
- Calculating the time difference between these two timestamps
- If the issue repeatedly entered and exited the same status, you'll need to sum up the individual durations

You can then compare your calculated value with the value reported by your current app to identify any discrepancies.

If you're looking to avoid manual calculations for multiple issues, consider using Time in Status Dashboard for Jira , an app developed by our company. This app accurately calculates time spent in status, including repeated entries and exits, allowing you to compare its results with your current app.

You can chose between a perspective where each time in status is present in a separate column or 

each status change is represented in a separate row

Not sure how you are extracting the data but this app allows you to export both perspectives in csv format.

One other thing you need to consider is if the status name you are mentioning could have been changed. There are various scenarios such as the status name changed once, or changed then changed back etc.

You will need to determine clearly from your History tab if this might have happened, which could explain "skipping" the status in a certain scenario. This can happen as you are not aware if the app you are using is using the status name or the status id (which does not change, even if the status name has been changed, and reflects as a changed status in the history).

Regards, 

Petru

[Yves Defossez]

Hi Petru,

Thanks for your answer.

I am extracting the "time in status" field from the rest API call to Jira.

This gives me the information of "status ID", "# enters into this status" and "time in status" so I only need to do a lookup of the status ID and I know how long a ticket has been in a certain status.

It is just that for one status this is not counting properly. Recently I found out that it seems to be the last status before the ticket reaches the end status. So when I added a new "in progress" status between the one I wanted and the end status, it does get populated. Still not sure why Jira is doing this.

[Danut M _StonikByte_]

Hi @Yves Defossez,

I am not familiar with the "google sheets addon" that you mentioned.

Perhaps the addon is right. Please look at the History tab of the issues to confirm that they have indeed gone through that workflow status.

If you don't manage to figure this out and the addon produces incorrect results, my advice is to search on Atlassian Marketplace for another add-on that is capable to display and export time in status. 

If you want to try another add-on, our Great Gadgets app offers a Time in Status gadget that can display various charts based in total and average time in status. In addition, it can display a Data tab with the time-in-status for individual issues, which can be easily exported in CSV format for further processing.

Danut

[Yves Defossez]

Hi Danut,

Thank you for your answer.

I have looked at the history tab and see that the ticket has gone through that status.

The workflow is a linear flow and all statuses need to be passed before a ticket can be closed.

I am not looking for another add-on at the moment as the one I am using does everything correct.

If I look at the API code of that ticket I see for the "time in status" field the same string as what the addon extracts. So I believe it is something inside Jira that is not registering the time in that "review" status.

Making a dashboard in Jira and inserting a pie chart does provide the correct timings for this status so why is the API code not giving the correct result?