Emre Toptancı [OBSS] Atlassian Partner

Hello @Kishan Sampat , For an automated solution that offers great flexibility and details, our team at OBSS built Time in Status app for these kinds of needs. 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.…

Hello @Jeff Davis , For an automated solution that offers great flexibility 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. You can…

Hello @Daniel Hurtubise , Yes, the report will show the total time spent in each status. EmreT

Hello @stephen.abiero , As @Ste Wright mentioned, our app Time in Status is built exactly for this purpose. It is an automated solution that offers great flexibility and details. 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…

Hello @Rafael Macedo , Time in Status is not part of standard Jira offering. It is available as a separate app on Atlassian Marketplace. You can see and install the app from the Marketplace link below: Timepiece - Time in Status for Jira Once it is installed on your Jira, you can access the app using the Time in Status…

Hello @Rafael Macedo , For an automated solution that offers great flexibility 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. You…

Hello Radek, For on-prem Jira editions, the DB table that holds this data is changegroupitem. All issue changes are in this db table so you will need to filter by issueID and status field. Getting flexible reports from this table is pretty tiresome. For a ready built solution that offers great flexibility and details, our…

Hello @Shubham v , If you are using Jira Software, Control chart in Kanban Board reports offer some visibility into this. It works with board columns rather that individual statuses and shows issues in a grouped chart rather than as individual issues. Custom calendar support is also limited but it can help you to get a…

Hello @JD Lobue , Jira does not provide this out of the box. If you are using Jira Software, Control chart in Kanban Board reports offer some visibility into this. It works with board columns rather that individual statuses and shows issues in a grouped chart rather than as individual issues. Custom calendar support is…

Hello @taylor.roberts , If you are using Jira Software, Control chart in Kanban Board reports offer some visibility into this. It works with board columns rather that individual statuses and shows issues in a grouped chart rather than as individual issues. Custom calendar support is also limited but it can help you to get…

Hello @Teh Kok How , Jira does not provide the report out-of-the box but you can use a marketplace app to get this. For a ready built solution, 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…

Hello @soumya wadhwa , Jira does not provide this information as a report from its user interface. If you can do custom development, you can use Jira REST API to get this data, one issue at a time. Since you are on Jira server, you can also query this data directly from Jira database. I don't know how you plan to use this…

Hello @Micaela Barros , I am afraid Jira does not have an out of the box solution for that. Your use case is a complex one and I am proud to say that we have a solution for that. Our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Server, Cloud and Data Center. Time…

Hello @Ahmed Alghamdi , Jira does not offer this out of the box but if you are interested in a ready built solution, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. The app contains 4 different date reports that show first/last entry/exit dates for all…

Hello @Ross LeMere , My first suggestion would be not to make deployments directly to pre-production or staging. If a bug is discovered on these environments (and decided to be fixed immediately), the source code is modified so it is a new deployment, a new package. This new deployment should start its life from the…

Hello @Jenny Thompson , JQL can only filter issues based on the criteria you provide. You see issue fields in the result set. JQL can't do calculations or manipulations on those issue fields, just returns what the fields contain. The raw data required to calculate ticket age is already available in each issue's history.…

Hello @somnath.yadav , If you need to only see WHICH issues were reopened, you can use a JQL query like @John Funk recommended. If you need to see HOW MANY times issues were reopened or find issues that were reopened the most, you will need to track reopen count. You can do this by configuration or by using an app. For…

You should go to Administration >> System >> Outgoing Mail to see if your outgoing mail server is enabled. If enabled, then go to Administration >> System >> Mail Queue to see if mails pile up in the queue and also check the Error Queue to see if there are any mails with errors. If you see issues here, you can go to…

Hello @Arunn Subbaraman Thyagarajan , As far as I understand, you want to see a list of issues with workflow status names as columns and the dates of entry to those statuses as values. Jira keeps these dates in its issue histories. You can see them in the History tab of each issue. I am afraid Jira does not provide this…

Hello @Csiszer Csongor , "How many issues a user resolved?" and "How long it took?" are actually two different questions. Let's approach them one by one. How many issue a user resolved? In order to get this report, you need to be sure that a field on the issue holds the name of the user that resolved the issue. If you…

Hello @Sérgio Hilgert Junior , I am afraid status duration data is a custom calculated data and needs a little more processing than simply transferring field value to sheets. The raw data you search for is available in each issue's history. You can see it in the History tab of each issue's view screen. But Jira does not…

Hello @Will McNelis , For a ready built solution that offers great flexibility 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…

Hello @[deleted] , Jira does not provide this as a ready-to-go report. You either have to calculate this yourself (by getting the raw data from REST API or DB tables) or use a marketplace app for this. For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status app for this…

Hello @codingouch , Unfortunately, JQL cannot do this out of the box. JQL can filter issues but it cannot compare dates on an issue or calculate duration between dates. I know this is not what you ask for but you can run queries to compare dates with current date. For example this query returns all issues that were created…

Hello @Swaroop , As others pointed out, this data is available in each issue's history but you will need to do some custom development to extract it and turn it into a report. For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available…

Hello @Sergii Delimarskyi and @Joe Pitt , For a ready built solution that offers great flexibility 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 contains reports that show how many times each status and each transition was…

Hello @Brad Chattillion , JQL can only do filtering and the result set will only contain field values on the issue. So getting the transition dates is not easy. If you want to build a manual solution (that works just by configuration), you can define custom date fields for each of the status dates you are interested in and…

Hello @fobrutsky , Sorry but Jira does not contain a ready report for this purpose. JQL is a query language but it is NOT like SQL. It can't do calculations, only filtering. JQL is a simplified version of the WHERE clause of SQL. And as a resultset, you can only get a table showing field values of issues. For Jira Server…

Hello @Karanpreet Kaur , Our team at OBSS built Time in Status app for this exact need and it offers different solutions for different use cases. 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 and count…

Hello @Vera Valshonok , If the users you speak about are non-Jira users, that means they won't have an option to update the issue themselves. Some other user (a real Jira user) will have to feed that data to the issue. This could be done by introducing two custom date fields and updating them manually or you can make one…