Emre Toptancı [OBSS] Atlassian Partner

Hello @Eileen McEneaney , Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. You can combine the time for multiple statuses to get…

Hello @Venkat Jira Admin , I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee. Time in Status offers two report types for…

Hello @Tata Tatkhashvili , The data required for such reports are available in each issue's history but Jira does not give these as ready-to-use reports. I suggest you use a marketplace app for these. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and…

Hello @Blake Falanga , Jira Product Discovery is keeping its ideas as Jira issues under the hood so any reporting that works for issues should also work for them. The closest you can get with out-of-the-box Jira is the Average Age Chart, which is available as a dashboard gadget. It is very limited in terms of details and…

Hello @Edgardo Ibarra, Building a custom automation will most likely be hard to build and maintain. So it will be expensive. I suggest you use a marketplace app for that. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status…

Hello @Thao Do Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. If an issue moves back and forth between statuses, by default, Time in…

Hello @Deepika Dandala , In Jira, Time in Status reports are not available as an out-of-the-box feature. I can suggest our app Timepiece - Time in Status for Jira by OBSS if you want to get such reports. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each…

Hello @Jamie Gordon , Jira does not provide this functionality out-of-the-box. All the data needed for this report is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira Server,…

Hello @Don Hames , Please note that our app, Time in Status by OBSS, does not have a free version. There are other apps with similar names so make sure you are trying the correct one. EmreT

Hello @Venkata Shanmukha Sai Rithvik Banka (HFQP74) , You can't get this report with a simple JQL because JQL queries can only filter issues. JQL can't make calculations on issue fields or history. Actually, the data needed for such a report is available in each issue's history but Jira does not present this as a…

Hello @Mariam Revishvili , A manual solution to calculate these times will be very hard (and so expensive) to build and maintain. It also won't work for past issues. Actually, the data needed for such a report is available in each issue's history but Jira does not present this as a ready-to-use report. I suggest you use a…

Hello @Neeraj Sharma Jira can't do this out-of-the-box. JQL queries can give you filtered results but JQL can't make calculations on issues and certainly can't process issue histories. Actually, the data needed for such a report is available in each issue's history but Jira does not present this as a ready-to-use report. I…

Hello @Urvi Bhor Actually, the data needed for such a report is available in each issue's history but Jira does not present this as a ready-to-use report. I suggest you use a marketplace app for this. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and…

Hello @Emery Manayan , Actually, the data needed for such a report is available in each issue's history but Jira does not present this as a ready-to-use report. I suggest you use a marketplace app for this. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud,…

Hello @lapacquah_bryant , The closest you can get with out-of-the-box Jira is the Control Chart (which is available as part of Kanban Board reports). However, Control Chart offers limited details and flexibility. For maximum details and flexibility, I suggest you use a marketplace app (I know you said you can't use an app…

Hello @Deepika Dandala Jira Control Chart offers limited details and flexibility in terms of report parameters. For maximum details and flexibility, I suggest you use a marketplace app. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time…

Hello @MANPRITSINGH , Actually, the data needed for such a report is available in each issue's history but Jira does not present this as a ready-to-use report. I suggest you use a marketplace app for this. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud,…

Hello @venkat g , Actually, the data needed for such a report is available in each issue's history but Jira does not present this as a ready-to-use report. I suggest you use a marketplace app for this. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and…

Hello @[deleted] , Jira Product Discovery works with the same Jira issues under the hood. Any app or report that can work on Jira issues can also be used for JPD issues. Our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows…

Hello @Don Hames Jira does not provide this functionality out-of-the-box. JQL queries can "filter" issues but they can't make calculations and they do not show transition dates as columns in their result set. The required data is available in each issue's history but you will need to use a marketplace app to get…

Hello @Robert McCool , You can do this with automation rules but it is very hard (and so expensive) to build and maintain. Actually, the data needed for such a report is available in each issue's history but Jira does not present this as a ready-to-use report. I suggest you use a marketplace app for this. If you are OK…

Hello @Rina Speciale If you want a more detailed and comprehensive report, you can use an app for it. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or…

Which add-on do you use the create baselines?

Hello @Ceejie Cecilia , I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status. Time in Status offers two report types for your case: The first one…

Hello @Jess Painter , Cycle Time is a valuable metric for all teams but since Epic'a are also issues, their workflows can be customized so the exact definition of Cycle Time is not the same for each Jira (It even might not be the same for all Epic on a single Jira instance). Let me recommend our app for flexible reporting…

Hello @Ankit Yadav , Try this: status CHANGED TO Done AFTER '2022-09-01 00:00:00' EmreT 

Hello @Mario Sanchez Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. By default, the app shows the total time issues visited each…

Hello @Venkata Shanmukha Sai Rithvik Banka (HFQP74) , JQL queries can only filter issues. JQL can't make calculations on issues. For that, you will need a marketplace app. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira exactly for this. It is available for…

Hello @Mayank Agarwal , There is no way to do this with Jira's built-in JQL queries because JQL does not care about weekends or weekdays. You'll need some kind of marketplace app that considers your custom calendars. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for…

Hello @Mohamed Saad Taha , Jira has no built-in mechanism for delegating permissions. Most people try to solve this by setting permissions based on assignees of issues and then changing assignees when people go on vacation. (There are actually some apps that automate this). There are several drawbacks to this approach. *…