As different stakeholders are involved in a project, how can I measure the time each of them take?

[Bhatt_ Reddhi Uday _external_]

Hi, 

So we have tickets that are handled by multiple stakeholders. Hence to determine the correct performance i.e. the time taken by each stakeholder to resolve the project is required. How is it possible to extract that in JIRA cloud?

[Gizem Gökçe _OBSS_]

Update on May 9th, 2024: Time in Status by OBSS was recently rebranded as Timepiece. It is still the same capable app with the same dedicated team behind it. The answer below mentions the app as "Time in Status" but you can find the app in the marketplace as "Timepiece (formerly Time in Status)". 

Hello @Bhatt_ Reddhi Uday _external_ ,

To keep track of the time spent on your issues by the stakeholders,  I recommend using a marketplace app that is specifically designed for this purpose. Time in Status which is developed by my team at OBSS, has a report type that will meet your need.  Our app is available for both Jira Cloud, and Data Center. 

Time in Status offers two report types for your case:

The first one is Assignee Duration or Assignee Duration per Status reports  which shows how much time each assignee spent on each Status. These reports show a list of issues by default so you can see the metric values for each issue separately. Please refer to the screenshots below.

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses. This report type also allows the user to exclude the times for "pause" statuses. You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

For example, in the screenshots below, the Duration Between Status report shows the total monthly response and resolution times for each assignee in a project.

   

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Visit Time in Status to explore how our JIRA add-on can revolutionize your metrics measurement process. 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.

You might also want to take a look at my latest article in the Atlassian Community.

I think this article can guide you on how to extract the data you need from your Jira and how to analyze it.

Recover Lost Time with Time in Status: Managing Blocked Tasks

Best Regards,

Gizem

[Amay Purohit_RVS]

Hi @Bhatt_ Reddhi Uday _external_ 

I can suggest our app to pull this data. You may want to have a look at it.

Time in Status Reports

The time in status report shows the time spent by your issues with each assignee during the entire workflow and easily track the total to get to your lead times.

The app has 20+ reports to track your bottleneck Issues & Processes.

More details here

Disclaimer : I work for the vendor who built this app

[Iryna Komarnitska_SaaSJet_]

Hi @Bhatt_ Reddhi Uday _external_ ,

I can advise you to try to estimate the time spent based on the time in status metric.

My team has developed the Time in Status for Jira - Reports | Charts | Dashboard app.

With it, you can calculate Lead Time, Cycle Time, Wait Time, and other metrics by creating status groups.

The app also offers seven types of reports to help you analyze your workflow:

• Time in Status,
• Assignee Time,
• Average Time,
• Status Entrance Date,
• Status Count,
• Transition Count,
• Time in Status per Date

We provide you with 30 days of trial to recreate different use cases.

I hope you find it useful!

[Rik de Valk]

Hi Bhatt, 

Can you clarify what you mean with 'time taken'? 

Do you mean actual time worked on a ticket (which is logged by logging time)? 

Or do you mean lead time (which is tracked by how much time has passed between 2 statuses (or created to resolved)? 

Kind regards, Rik 

[Bhatt_ Reddhi Uday _external_]

Hi Rik,

It is the time that is logged by the logging time;

For example each ticket is assigned to different stakeholders A, B and C for the resolution of ticket X .

if ticket X has a total lead time  of 3 days  where A, B and C were assigned the ticket at different points in time between the creation and resolution of the ticket , how do i track the time taken by A, B and C each to have the total lead time as 3 days. It would be useful to extract it for all tickets. 

Is there a way to measure the time take by A, B and C individually to resolve ticket X?

Kind regards,

Reddhi

[Rik de Valk]

Well, logged time and lead time are 2 different things. 

The total [lead time] = [processing time] + [waiting time]

But [waiting time] is not logged. So the sum of all [processing time] which is logged will never add up to the total [lead time]. 

You could consider creating Sub-task for each stakeholder. This way you clearly distinguish between each activity. And you can use the resolution time as the total lead-time. 

[Bhatt_ Reddhi Uday _external_]

Hi Rik,

Thanks for the feedback! I shall try this!

Kind regards,

Reddhi