Useful statistics

I would like the possibility to get some statistics based on actual activity in jira, and the real time to deliver, not by logging of time actually worked on the issue.

* Keeping time: Extract how long an issue actually is assigned to an assignee (or a group of assignees)

* Progress time: Extract how long an issue spends within a defined status or between two defined statuses

* Perhaps also a possibility to combine these two in a way, for instance to see how much time it is assigned to reporter from it is put in progress and until it is resolved.

The data should be possible to export to make it possible with further calculations and filtering. It would be nice with the possibility to aggregate the data before it is reported

We handle multiple projects so it should be possible to query across projects. It would also be helpful if the data can be filtered based on labels (Small, Medium, Large)

This will make it possible to get reasons for our time to delivery today and also what can be done to limit this time in the future.

UPDATE: A clarification. My main goal is to handle this across multiple cases. I have some nice answers that would be very helpful for each case, but still requires a lot of manual work to get statistics for all the relevant cases.

Basically I believe my problems regarding spent time would be solved if the cumulative flow diagram in Rapid Board was available as a data table. There I can see the transitions for several cases, even refine the selection, but I just can't access the data only inspect the results visually.

Likewise getting the transitions between assignees the same way would help me calculating what I need in that area.

5 answers

1 accepted

0 votes

Answer accepted

Had totally missed about this plugin which may satisfy you. Check out https://studio.plugins.atlassian.com/wiki/display/JSUTIL/JIRA+Suite+Utilities+Issue+Transitions+Tab

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

This is exactly what I need, except it seems to be available only in every single issue. I am looking for the possibility to export from a lot of cases, so that I can calculate based on that.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

There is a custom field in 'Jira Misc Custom Fields', which can return the date/time at which a transistion has happened "Transition Date/Time Field". Adding it for the transistions that you are interested can help you to take it out from a Jira filter. And a simple Excel to do a difference between the values of different transistions should work. Just an idea.

https://studio.plugins.atlassian.com/wiki/display/JMCF/Home#Home-transitiondatefield

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I see that this theoretically can solve my needs. However I am not sure i will manage to get a jira developer to implement this. It will also require several custom fields that may create visual noise to those who use jira every day.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

You need not do any development, you can use the plugin. And regarding your second question, any solution that gives this value out of a filter will require a custom field and everyday users will see them.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Perhaps I can try digging into this some more once I get the time. It's not immediately clear to me all I have to do to reach my goals. However this suggestion seems to have a lot of potential. I just have to figure out how to realize it.

I was hoping something existed that gave me the table more "out of the box", since analyzing trends in time spending was assumed to be useful for many, and the data was available only in wrong format in the CFD-chart in RapidBoard. However it seems it wasn't that easy after all.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Welcome to Atlassian products!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hey everybody,

i'm using jira misc custom fields "Transition Date/Time Field" so i can get the date issue was closed. Works fine. When i'm exporting the results in Excel i'm getting only the date, there is no time for the custom field.

Did anyone have the same problem?

Cheers,

Kostas

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Instead of the built-in Jira "export to CSV" feature, use our (paid and supported) Better Excel Exporter app. It can correctly export all Jira Misc Custom Fields field type to native Excel spreadsheets. See this tutorial page.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

1. If you are looking at average values, you can get this by using "Average Time in Status" from Jira Charting Plugin

2. If it is average resolution time, you can also use the direct "Resolution Time" chart.

3. And to see a trend whether the team is able to handle the inflow, the 'Created vs Resolved' chart really helps.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you for your quick response. This seems to focus on charts more than tables. For some of the charts a "detailed data dable" seem to be available. For others it seems to end with the chart. It is important for me to get access to the data and not only inspect a visual graph.

If you know the Jira Charting Plugin perhaps you might tell me if it also gives me information about the time spent assigned to defined assignees too.

It doesn't seem to give me time between two statuses out of the box, but I assume I will get my data by adding average time within the different statuses, at least for cases with the same workflow.

What defines "resolution time" in the chart? It may be interesting if it is defined from when a case is picked (InProgress) , but will be less relevant if it uses create. Issues may be created and have low priority for a long time, and then the result will be affected by the types of cases more than the efficiency in the team.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

Thanks a lot Andrey, this was very close to what I need. It gives a nice overview over where the time has gone for an issue. We tried to install it, but we couldn't find a good way to aggregate the information to a common report. So it was close, but just not close enough to keep ;-)

One main reason why we chose not to keep it is that since first request we have made ourselves an extraction tool that exports time in status to an external database.From there I'll get (almost) all the reports I need. Since we aggregate time in status and not between statuses we're not as vulnerable to quirky flows of the issue, seemingly a problem for some approaches (like https://confluence.atlassian.com/display/AGILE/Viewing+the+Control+Chart ).

Now I can summarize all the "in progress" type statuses to see how long period this was actually on board, not being affected by periods with no progress (like ToDo, Resolved, Closed, impeded etc). I can also see detailed overview for each status, and drill down to see which issue(s) that causes most delay. If some periods shows bad progress data, I can drill down to see which issues caused it and why. This gives us more power to analyze the flow of issues over time and get a good focus on bottlenecks.