Gizem Gökçe (OBSS) Atlassian Partner

Hello @Vera Valshonok , The required data is available in each issue's history but to get ready-to-go reports the easiest option is to use a 3rd party app. I understand that you are not looking for a paid solution right now but in case you need it these reports are available in Timepiece - Time in Status for Jira , the…

Hello @Jayanth , I've noticed that you are on free plan in Jira. So if you ever decided to consider 3rd party apps to track how much time each story spend on each status and create detailed reports you can use Timepiece - Time in Status for Jira, developed by my team at OBSS, free of charge. Timepiece automatically…

Hello @Vera Valshonok , To track how long each ticket was open and create detailed reports, I recommend using Timepiece - Time in Status for Jira, developed by my team at OBSS. Timepiece automatically calculates the total time tickets spend across their lifecycle or within specific statuses, such as from creation to…

Hello @Petru Simion _Simitech Ltd__ , Hello, You're absolutely right that workflows can vary greatly, and simplistic assumptions about statuses often fail to capture these nuances. Accurate Cycle Time and Lead Time calculations should consider: * Custom starting and ending statuses. * Exclusions for pause statuses (e.g.,…

Hello @ali.salem , Welcome to the community! I am the product manager of the app Keychain - Delegation for Jira which @Marc -Devoteam- also suggested above. By using Keychain you can easily delegate permissions in your workflows and JSM Customer Portal Approvals. Once a delegation is defined or modified, assignees or other…

Hello @Nico , If you want to calculate the time spent in each workflow status automatically, you’ll need to use a third-party app that specializes in such metrics. One such app is Timepiece - Time in Status for Jira, the oldest and leading 'Time in Status' app in the Atlassian Marketplace, developed by my team at OBSS.…

Hello @Mathew Kuruvilla , Tracking the time spent in specific workflow statuses (like Programming, Analysis, Queue, etc.) is not directly possible with Clockwork Pro, as its primary focus is time tracking via worklogs rather than automatically calculating time spent based on issue history. Clockwork Pro is excellent for…

Hello @Ken Rupin , Welcome to the community! What you're describing is a cycle time metric, which tracks how long it takes for a ticket to move from one defined point in the process to another—in your case, from when it’s assigned to a team member to when it reaches the "Resolved/Closed/Done" status. However, Jira doesn’t…

Hello @Vera Valshonok , Jira's native functionality doesn’t provide a direct way to calculate time spent between two statuses while skipping certain intermediate statuses. With Jira’s built-in tools, you can track the total time spent in each status using reports like the Control Chart. However, it doesn’t allow you to…

Hello @Lubna Malik , You can get a basic count of how many times tickets transitioned from “QA” to “In Progress” using a JQL query in Jira. Here’s a quick way to do this: JQL Query: You can use the following JQL query to see all tickets that have transitioned from “Dev” to “Testing” at least once: status changed…

Hello @Richard Cieslik , Welcome to the community! Tracking specific status change dates, like when tickets moved to “Delivered” in the past 7 days, isn’t possible with native Jira fields, as there’s no dedicated "Status Change Date" field. Status changes are only stored in the issue history, and native Jira doesn’t allow…

Hello @Gregory Carman , Unfortunately, native Jira does not provide direct reporting on how long an issue has spent in a specific column or status. So in order to track the time spent on each status & each assignee I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in…

Hello @LUIS MIGUEL DAZA MENDOZA , Welcome to the community! You can use JQL to find issues that have been in the same status for a specific time range, such as more than 2 weeks but less than a month. Here’s how you can do it: JQL Query: To find issues that have been in the status "X" for more than 2 weeks but less than a…

Hello @Vandana , You can get a basic count of how many times tickets transitioned from “QA” to “In Progress” using a JQL query in Jira. Here’s a quick way to do this: JQL Query: You can use the following JQL query to see all tickets that have transitioned from “QA” to “In Progress” at least once: status changed…

@JiraLearner Yes, Timepiece has a REST API, so you can pull data from it and use this data within other tools. While we don’t have in-depth knowledge of Structure by Tempo’s specific setup, you might find useful guidance on the process in Tempo's support page here. Please feel free to reach out if you have any other…

Hello @Rémy Hilbert , Welcome to the community! Yes, you’re correct! In Jira, the Control Chart is typically used to measure Cycle Time in Kanban. It shows the time issues spent in each status, helping you visualize flow efficiency. However, as you mentioned, the Control Chart can sometimes be difficult to interpret and…

Hello @Marija Simic , Welcome to the community! Jira’s default average age gadget calculates from the ticket’s creation date rather than from a specific status. This limitation means there isn’t a straightforward way to start measuring age from "To Do" within native Jira. To achieve this level of customization, a…

@JiraLearner to answer this, can you clarify your expectation a bit? Do you want to extract data from Timepiece and put it into Structure by Tempo? Or do you want to create reports on Timepiece using the data from Structure by Tempo? If you could give some details about your exact need, it will be easier for me to guide…

Hello @JiraLearner , Many teams struggle when users forget to log their work, so it is wise to use a reporting system that tracks how long issues remain assigned to individuals or measures the time spent on each status. This method will help you forecast effort and productivity. To track the time spent on each status and…

Hello @Jacob I , Welcome to the community! If you’re ok to use Jira add-ons, Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has several report types that will meet your need. Our app is available for both Jira Cloud, and Data…

Serkan Bey Merhabalar, @serkan_sezer Kişilerin worklog girmeyi unuttuğu durumlarda (ki tahmin edersiniz ki bir çok yerde bu sık yaşanıyor) kendi eski çalıştığım kurumda assignee üzerinde bir issuenun ne kadar kaldığına dair bir raporlama ve bu veriler üzerinden efor çıkarma/tahminleme sistemine geçmiştik. Belki siz de…

Hello @Sushmita Chakraborty , In order to track the time spent on each status & each assignee I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has several report types that will meet your…

Hello @Pieter Koelewijn , Welcome to the community! I think what you are trying to see is the resolution time of a resolved issue and how much time each assignee spent on each issue and combine them on a weekly basis to measure team productivity. In order to measure metrics like Cycle Time, Lead Time, Resolution Time I…

Hello @Peter Walowen , One of the best ways to track the time spent on certain tasks is to dig into the Jira issue histories. Tracking the time spent on each status & each assignee can give you a good overview of the effort spent. To track this let me suggest you a marketplace application. Timepiece - Time in Status for…

Hello @SianS , As @Walter Buggenhout noted OOTB Jira requires Jira users to log time to track time spent. If it is not possible for people to enter logs into the system, I suggest you track the time spent on each status or assignee in a Jira workflow to get clearer measurements. For this I want to suggest a Marketplace…

Hello @Whitney Nicholes , I worked as a JIRA administrator in the defence industry for 10 years and we had a lot of different project management teams using JIRA. At that time all the teams used Timepiece - Time in Status for Jira to track process performance and identify bottlenecks in their projects. For the past year, I…

Hello @snehil.mishra , For that I can suggest you a marketplace app which will give you ready-to-go reports. Timepiece - Time in Status for Jira ,the oldest and the most comprehensive "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type that will meet your need. I've seen…

Hello @jriccardo , In Timepiece - Time in Status for Jira you can export the reports in to various formats easily such as CSV and XLS. You can import these data in your external databases if you need. Please see the screenshot below. Also the app has a REST API so you can get the reports via REST. You can find detailed…

Hello @Jenny Piléus , Welcome to the community! For that I can suggest you a marketplace app which will give you ready-to-go reports. Timepiece - Time in Status for Jira ,the oldest and the most comprehensive "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type that will…

Hello @Someswara Kudumala , Welcome to the community! As @Eduardo states above there is no built in solution in Jira for this. So in order to track the time spent on each status & each assignee I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian…