How do you create cycle times that include linked issues?

Question

Hey folks,

I'm working on trying to find a way to see all of my open tickets in JSM and tie them to open linked issues and calculate things like lead and cycle times.

For example, if I have a JSM ticket open and it's aging, I'd like to know what the hold-up (or hold-ups for multiple tickets) is and be able to identify how long those hold-ups have been an issue.

My current thought is to extract all of my JSM tickets into Excel (done, shows me age and last update values of the JSM ticket). I can even show the various linked issues, but I cannot see age of those linked issues.

My next step was to pull a list of all of the linked issues and get things like created date, updated date, and resolution date--but JQL doesn't seem to have an easy list from which to pick.

Just curious if anyone else has run into something like this and found an acceptable resolution. Ultimately, customers don't care why an issue is aging (nor do I blame them) but I'd like to know so that I can better work through achievement of SLAs, etc.

Thanks all!

-Chris

Gizem Gökçe (OBSS) · Answer

Hello @Christian Jordan ,

Listing issues with their linked issues is in our current roadmap but, I can tell you how to calculate total cycle times and provide you a workaround for listing linked issues while this feature is being developed by my team at OBSS.

You can calculate Cycle Time by using, Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace. Our app is available for both Jira Cloud, and Data Center.

Timepiece mainly allows you to see how much time each issue spent on each status or each assignee.

Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select.

Important Note: As you can see from the screenshots above, I've used a custom JQL to list both the linked issues and the original issue itself. So if you want to calculate the total cycle time of a particular issue, including the linked issues, you can use the method I've used in my example.

Here is the JQL:

issue in linkedIssues("GIZ-16") or issue = "GIZ-16"

Visit Timepiece - Time in Status for Jira to explore and enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

Christian Jordan_8exl8w · Answer

Excellent. Thanks for the suggestion!

-Chris

Valeriia_Havrylenko_SaaSJet · Answer

Hi @Christian Jordan 👋

Cycle times that include linked issues are in our features requests. But now you can calculate lead and cycle times precisely with Time in Status add-on.

To get total duration, all you need is to:

* create a status group;
* choose statuses;
* click the "Save" button.

Add-on has 30-days trial version, free up to the 10 users and developed by my SaaSJet team.

I hope this helps 😊