Emre Toptancı [OBSS] Atlassian Partner

Hello @Sharona Keren , I believe you can get useful reports on this using our app Timepiece - Time in Status for Jira. Mainly, Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee but it also has date reports that show first/last entry/exit dates for all statuses. For…

Hello @Giuseppe Costa , You can get this data using our app Timepiece - Time in Status for Jira which also introduces REST API endpoints for BI integrations. Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. You can…

Hello @bala , I believe Resolution-Time report is available only for Classic projects. You won't be able to find it for Next-Gen projects. There is a built in Resolution-Time Gadget though which serves the same purpose. You can maybe try that one. It is worth noting that these reports only daily, weekly, etc averages of…

Hello @Maranda Zwieschowski , First let me tell you that I agree with other people who ansered this question. The healthy way to get this data would be to log time on issues. Having said that, the next best thing would be to see how much time each issue spent on each status and aggregate this per Epic. For a ready built…

Hello @s.kern , You can see individual actions on an issue in each issue's History tab. Other than that, I am afraid Jira does not offer an ready report for this. You can use custom fields to count the number of status visits. To do that you need to define a number custom field for each status you want to follow. Then…

Hello @Sami Ahmed Shaik , I am glad to hear that you found Time in Status useful. If you send an e-mail to our support team at plugin@obss.com.tr , I can make sure that our team informs you as soon as the gadget is released. EmreT

Hello @Tim Bäßler , I am afraid what you are looking for is not available out-of-the-box in Jira. Each issue shows its own history under History tab but it is only for a single issue. As for JQL, it is only used to filter issues. JQL cannot perform calculation or show issue histories. You can only add fields on issues as…

Hello @Sami Ahmed Shaik , I am afraid what you are looking for is not available out-of-the-box in Jira. Each issue shows its own history under History tab but it is only for a single issue. As for JQL, it is only used to filter issues. JQL cannot perform calculation or show issue histories. You can only add fields on…

Hello @Uma Sanjeevi , Thank you very much for the feedback. It is very very important for us. Since we cannot get your direct contact information from here, can you send these items as an email to plugin@obss.com.tr so we can start a conversation with you to get more details. Best regards, EmreT

Hello Thomas, Jira does not offer this functionality out of the box. To get such a behavior, you can use a custom date field. let's call it "Current Status Date". You can modify your workflows and use the "Update Issue Custom Field" post function in each transition to write the date of transition to "Current Status Date"…

Hello @jira_admin_cu , Our app Time in Status might help you about this. Besides giving reports about how much time each issue spent on each status, assignee or group; Time in Status also gives reports showing the first/last transition dates for each status of each issue. The app works by processing your existing Jira…

Hello @unnikrishnan , I am afraid this data is not available as a ready to get report on Jira. The raw data is available in the history of each Jira issue but you would need to get the data from each Jira issue with a REST call and do the calculation yourself. Not an easy development. For a ready built solution that offers…

Hello @dimitar_filipov I am afraid this data is not available as a ready to get report on Jira. The raw data is available in the history of each Jira issue but you would need to get the data from each Jira issue with a REST call and do the calculation yourself. Not an easy development I must say. I also should say that the…

Hello @Vinay Dhuri , I am afraid this data is not available as a ready to get report on Jira. The raw data is available in the history of each Jira issue but you would need to get the data from each Jira issue with a REST call and do the calculation yourself. Not an easy development I must say. For a ready built solution…

Hello @Joan O"Neill , I am afraid this data is not available as a ready to get report on Jira. The raw data is available in the history of each Jira issue but you would need to get the data from each Jira issue with a REST call and do the calculation yourself. Not an easy development I must say. For a ready built solution…

Hello @Anuradha Yadav , You can see this data for individual issues under each issue's History tab. I am afraid there is no out-of-the-box way to display this data as a column in Issue Search page. In order to to this, you would need to do some heavy lifting. You would probably create custom date fields to hold each date…

Hello @Zoe Barr , I am afraid, Burndown Charts are available only for Scrum Boards. The good news is, you don't have to switch to another project/board alltogether just to use the Burndown Chart. Since a Jira Board is just an interface to your existing issues, you can create a new Scrum board as a second board to your…

Hello @hendri juniari , If you are using Jira Software, the Control Chart that is available as a part of Kanban Boards might help. You can get report of time your issues spent in each column of your board. Control Chart is a high level solution and will give you an overall picture of things. I think it is a little hard to…

Hello @Vinay Sharma , The Control Chart which is available in Kanban Board reports, provides a high level solution. I think it is a little hard to work with since: * Lack of control over reporting details * Inability to work with individual issues or statuses * Not being able to get the raw data Even so, if might be enough…

Hello @Shathya Bhama V R , Unfortunately Jira (or Confluence) does not provide this functionality. For Jira Cloud, you would need to get the data from Jira REST API and do the calculation yourself. For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app for this exact…

Hello @Ashok Chotai , Our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can calculate averages and sums of those durations grouped by issue…

Hello All, This is a pretty old post but since you guys are following, let me give you some detail: The data that can be used to produce reports like Issue Age, Cycle Time, Lead Time are Issue History Data but Jira does not give these data in a UI report. For Jira Cloud users, you can get this raw data through REST API.…

For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit…

Hello @Gabriel Carvajal , JQL only allows you to filter issues based on given criteria. Each row in the output represents an issue and the columns you can show in issue search page are issue fields only. Unfortunately there is no out-of-box option to display information from issue history and/or related issues. Since you…

Hello @Luis Zuniga For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well…

Hello @Mike D , If you are interested in a ready built solution, our team at OBSS built Timepiece - Time in Status for Jira app for this need. It is available for Jira Server, Cloud and Data Center. Time in Status contains 4 different date reports that show first/last entry/exit dates for all statuses. The app also gives…

Hello All, This is an old question but I see that it has been seeing a lot of action lately. For anyone here who are interested in a ready-to-go solution, our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center. Using Time in Status you…

Hello @Rado , Our app, Timepiece - Time in Status for Jira, might help you with this. Time in Status mainly shows how much time each issue spent on each status or each assignee. but currently it reports the total time for each status. Getting status times for each micro-cycle is not directly available but there are some…

Jira does not care much about that field being on the form or not. If it is required, it is required. You should check your Defect issue's Field Configuration and workflow's Create transition to see it Team field was made mandatory.

Hello, The only way to do this as you describe it would be developing some custom code, which is complex. The sensible solution would be to make sure your Epic workflow reflects your stories' workflows and still make the measurement based on Epic workflow. I suggest you configure your Story workflows to make the linked…