Need to measure when Issues change their TYPE... Looking for Help

[Ed Richard]

There is a ton of info on measuring/counting how long an issue has been in a certain status, or switched status or other transitions, and I'm pretty good with this stuff but I can't come up with a calculated measure to know when an issue change from one issue type to another (the specific types don't matter.. in my case our support group flips issue types based on a number of factors and want some analysis around this). I am importing issue history and have tried to model all those many measures related to status (such as days in transition status) and edit them for issue "type" but have been unsuccessful after > 20 hours of trial and error. Can anyone provide the calculated measure code I may need to count this kind of transition? (such as how many issues changed type in a certain time period and the average time issues remained in a certain issue type?).. Thanks in advance

[Petter Gonçalves]

Hello Ed,

Natively, there is no way that you can return this kind of information on JIRA, however, there are some options that could work for you:

1 - You can use JQL tricks plugin with the function movedIssues([type],[From],[To]),

as you can see in this documentation:

- J-Tricks documentation

2 - If you are on JIRA Server, you can get this information directly from the database, as described in the documentation below:

- How to List Issue Type changes of Issues in JIRA

3 - You can use different statuses across your workflows, so you could use the status change measuring/counting to identify any issue moving.

[Ed Richard]

Hi Petterson,

Thanks for the reply..I did download and use the JQL tricks add-on which got me to the point where i can filter for which issues changed their type (which is a start). Knowing how many days it was in each type is the remaining challenge and maybe your #3 bullet point above helps with that but I honestly don't know what you mean in terms of status having a connection to type changes and how you would drill into that for the data I need... anything else you could share would be greatly appreciated.  - Ed

[Petter Gonçalves]

Hello Ed,

The third option that I suggested would be to use different statuses on your workflows and would not need any plugin.

So, let's suppose that you have two workflows:

- To Do, In Progress, Done

- Start - Progress - Resolved

For the situation above, you would be able to use one of the methods to measure the changes between statuses and since both workflows have different statuses configured on, you would be able to track when the issue was moved from one workflow to another.

E.g: From To Do to Start.

Anyway, it would still be a challenge to know how many time your ticket has been spent on each type.

The only workaround I can think to make it work would be using the time reports plugin which gives you how many time an issue has spent on which statuses, however, you would still need to sum up the time of the statuses in the same workflow in order to get the total amount.

I'm really sorry that we don't have a better option to achieve it yet, Ed.

Please, let me know if you find a better option or have any questions about my suggestion.