Gizem Gökçe (OBSS) Atlassian Partner

@thumuluru.shreya What you are actually asking for is not the average of a single ticket. The average of issues linked to an issue. In Timepiece, there is no option to group issues by issue links, due to technical difficulties caused by bi-directional issue links in Jira. However, I can suggest a workaround. If you can put…

Unfortunately there is no way to calculate the average time of a single issue in Timepiece. You can only calculate averages by grouping issues with their specific issue fields. Can you please tell me the use case behind this feature request? I would like to understand it fully so that I can perhaps offer you a different…

@thumuluru.shreya You can use the total time spend column and divide it manually to the sum of statuses if you need an average for a specific single issue. In timepiece there is no average time calculation for single issues right now.

Ok now I think I understand what you mean. @thumuluru.shreya In this case let me tell you about our Drill Down option. I think this will meet your need. While working with Aggregate Reports (Average, Sum, Median, Standard Deviation), you can use the drill-down function on each report row to see the issues that made up that…

@thumuluru.shreya from the Report Options menu you can either take the average duration or the sum of the durations of the grouped issues. So in this case what must be done is you will prepare 2 separate reports (one for sum one for average).

Hello @thumuluru.shreya , You can use the Statuses menu to do this. In this menu you can add the statuses you want to see in your report. From the same menu you can also add a consolidated column and add the statuses you want under that column to get the total average. See the screenshots below. Main Screen Config: Gadget…

Hello @thumuluru.shreya , Welcome to the community! I can suggest 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. All the reporting features available on the main screen of our application are also available on our dashboard…

Hello @Jacqueline N McCluer , The required data is available in each issue's history but you will need to go through every issue one by one to dig out this data or create your automated solution by using Jira REST API. Lastly, the best and the easiest way to achieve that data is to use a marketplace app to get ready-to-go…

Hello @thumuluru.shreya , Welcome to the community! Listing issues with their linked issues is in our current roadmap but, I can provide you a workaround for listing linked issues while this feature is being developed by my team at OBSS. In this response , I will mention the app Timepiece - Time in Status for Jira ,the…

Hello @Sharon , The required data is available in each issue's history but you will need to use a marketplace app or develop your own solution with Jira REST API to get ready-to-go reports. If you are ok to use a 3rd party app, that report is available in our application where you can directly learn the transition dates…

Hello @Tom Rosenberg , Welcome to the community! There is no built in solution in Jira for this. So in order to track the time spent on each status 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…

Hello @Anurag Chavan , I believe Timepiece - Time in Status for Jira which is developed by my team at OBSS, might solve your problem. 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. For all numeric report types in…

Hello @K_ , I didn't understand from your question what method you use to keep track of time spent on tickets. Normally you have two options here. One is to use the time logged by the users. However, this is not always ideal as team members tend to forget to log the time spent on issues, or in this case, tickets. Your…

Hello @Sampath , Timepiece app has the report types (Assignee Duration and Assignee Duration per Status reports) that I've talked about in my previous answer for Jira Data Center as well. Our app has the same features for both Data Center/Server and Cloud. You can start using it right away. You can get an evaluation…

Hello @Sampath , Unfortunately, these features aren't available in Jira out of the box. JQL doesn't have this capability either. You can get the data from each issue's history, but you have to build your own code or use a third-party app.

Hello @Sampath , In order to measure everything that you stated above I can recommend Timepiece - Time in Status for Jira app, the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Cloud, and Data Center. Timepiece mainly allows you to see how…

You are welcome! Timepiece - Time in Status for Jira also has a very capable REST API. This means you can get the data via REST and import the result to an external reporting tool. Have a nice day!

Hello @Jackie hardy , In order to measure and track your agents performance I would recommend using a third-party app, as there is no built-in report in JIRA for this. My recommendation is Timepiece - Time in Status for Jira app, the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team…

Hello @Hajar Shalaby , Welcome to the community! In order to measure and track your developers performance I would recommend using a third-party app, as there is no built-in solution in JIRA for this. My recommendation is Timepiece - Time in Status for Jira app, the oldest and leading Time in Status app in Atlassian…

Hello @Nithin Ammisetty , Welcome to the community! You are correct, the required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Good news that report is available in our application where you can directly learn the transition dates without having to deal…

Hello @Tarieli Gvritishvili , As I do not understand exactly what you will be using this data for, my answer may be irrelevant, but if your purpose is to create a report, the required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Good news that report is…

Hello @Marquis Harris , Welcome to the community! I believe Timepiece - Time in Status for Jira which is developed by my team at OBSS, might solve your problem. 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. You…

Hello @Mike Oragwa , I want to offer you another perspective. In order to track your teams performance it might be useful to track and measure some common metrics such as Cycle Time, Issue Age, Resolution Time etc. I would suggest that you read my article on these metrics if you are unfamiliar with the concept. Revealing…

Hello @Jack Richens , If you are open to use a marketplace app I can suggest you a solution. 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 a report type that will meet your need. Our app is available for both Jira Cloud,…

Hello @Camille DeGuire , Welcome to the community! Our 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 a report type that will meet your need. Our app is available for both Jira Cloud, and Data Center. Timepiece mainly…

Hello @Prajakta Marotkar , Welcome to the community! If you ever consider using a marketplace app to calculate the Issue Age for your issues, I can recommend Timepiece - Time in Status for Jira , the oldest and leading "Time in Status" app in Atlassian Marketplace, which is built by my team at OBSS. It is available for…

Hello @BHANU TEJA , Time to first response and time to resolution are what we call SLA's and SLA feature sets are specific to JSM. So, unfortunately, you cannot configure them the same way in Jira because those features aren't available there. However, you can use a third party app to achieve the First Response Time and…

Hello @Cristóbal González , The app that @shivakumarh483 mentioned is Timepiece - Time in Status for Jira , the oldest and leading Time in Status app in Atlassian Marketplace, which is built by my team at OBSS. It is available for both Jira Cloud, and Data Center. You can use the date-based reports to see the transition…

Hello @daniel.ouyang , Welcome to the community! The required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Good news that report is available in our application where you can directly learn the transition dates without having to deal with Jira issue…

Hello @Iris Ayelin , There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. I can recommend Timepiece - Time in Status for Jira , the oldest and leading "Time in Status" app in Atlassian Marketplace, which is built by my team at OBSS. It is…