Emre Toptancı [OBSS] Atlassian Partner

Hello @Krisna Leo Parista If your developers are updating their Jira issues on time (for example if they move the issue to InProgress as soon as they start working, move to resolved as soon as it's done, and always assign the issue to the relevant person immediately) you can use the status and assignee times of issues to…

Hello @Aisha Kantharia I think I got the perfect thing for you, our team at OBSS built Time in Status app for this 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 also combine statuses…

Hello @Pablo Bernardo Jira does not give this information out-of-the-box but I think I got the perfect thing for you. 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…

While this is technically possible, I'm afraid in most cases it won't help. Because getting the Epic name of the parent is only a part of my total work with the issues. If I rephrase the query to include the parent issues, I won't be able to tell if any parent issue was in the resultset of the original query or it was…

Hello @Liesl Jordaan I think I got the perfect thing for you, our team at OBSS built Time in Status app for this 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 also combine statuses…

Hello @Brenda Higgs First of all, I want to say that I agree with the other answers. Making entering worklogs is the most healthy way of getting data for future estimation. People in your organization are like production machines in your factory. You want to know what they spent their time on. The next acceptable thing…

Hello @atarab I suggest you take a look at Atlassian's Advanced Roadmaps. It is built exactly for such use cases. It allows you to take a sum of estimations from sub-task level to stories, epics, and further (it even allows you to define levels above Epics.) And about turning original estimation into worklogs via…

Hello @Shams Jira does not give this information out-of-the-box. The data you need is available in each issue's history but is no presented to the user as a report. Since you are on cloud, you won't be able to access the DB to get this data out but you can build such a report yourself using the REST API (requires some…

Hello @James Hill 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 also combine statuses into consolidated columns to see metrics…

Hello @Nguyễn Thị Hảo I am afriad, this cannot be done directly with a JQL query. You will need to make your custom configuration to measure this or use one of the marketplace apps. In case you are OK with using a marketplace app, our team at OBSS built Timepiece - Time in Status for Jira app for this exact need. It is…

Hello @Bret Justus If you rather now spent time on building and maintaining a custom configuration, 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 in Status allows you to see how much time each issue spent on each status or…

Hello @[deleted] 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 also combine statuses into consolidated columns to see metrics…

Hello @Pranita Warik 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 in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can also combine statuses into consolidated…

Hello @Felipe Rodrigo P. P. de Lima , 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 also combine statuses into consolidated…

Hi @Oiran Leite , Unfortunately, this is not possible with JQL. You will need to make a workflow configuration to manually measure this yourself or you can use a marketplace app for that. 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…

Hello @Wojciech Cora , 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. For your case, you can select your issues and see how much time each one…

Hello Everett, For this problem, the first thing to focus on would be to CREATE the correct data rather than how to report on it. Since you want to see how much time was spent on something, you can either do this through work logs or the following workflows of issues. If you choose to do this with work logs, you will need…

Hello @uday 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 in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can also combine statuses into consolidated columns to see…

Hello @Cameron Mitchell You can use the built-in Control Chart (that is available as part of Kanban Board reports) about this but it is not very good with reopens. It will show you durations but it won't show individual issues. It is more aimed towards seeing the big picture. Plus, you can't get its raw data. There are the…

Hello @James Phillips That is one of the limitations of the built-in Control Chart. It will show you durations but it won't show individual issues. Plus, you can't get its raw data. It is more aimed towards seeing the big picture. In case you are OK with using a marketplace app, our team at OBSS built Timepiece - Time in…

Hello @Hoc, For status transition dates of individual issues, you can see each issue's History or Transitions tabs. For Assignee changes, you can also see Issue History Tabs. These data are not available as field values so it will not be possible to see them in Jira issue search screen. You can try creating custom fields…

Hello @Stefano Susini There are some solutions worth mentioning here: You can use the built-in Control Chart (that is available as part of Kanban Board reports) about this but it is not very good with reopens. It will show you durations but it won't show individual issues. It is more aimed towards seeing the big picture.…

Hello @Clicker I am afraid there is no way to do this out-of-the-box and but there are some solutions worth mentioning here (surely not part of an eazyBI solution as presented here): You can use the built-in Control Chart (that is available as part of Kanban Board reports) about this but it is not very good with reopens.…

Hello @Steve Steve I am afraid there is no way to do this out-of-the-box. Yet, there are some solutions worth mentioning here: You can use the built-in Control Chart (that is available as part of Kanban Board reports) about this but it is not very good with reopens. It will show you durations but it won't show individual…

Hello @Manoj Khaire, I am afraid there is no way to do this out-of-the-box. Yet, there are some solutions worth mentioning here: You can use the built-in Control Chart (that is available as part of Kanban Board reports) about this but it is not very good with reopens. It will show you durations but it won't show individual…

Hello @Daniel Satnic That is one of the problems with the built-in Average Age Report or Resolution Time Report. Both reports also are very high level. They just show daily average data. Average Age Report excludes resolved issues and Resolution Time report excludes non-resolved issues. Resolving an issue dramatically…

Hello @Lee Street I can recommend our tool Time in Status. You can use it to identify bottlenecks in your process and also see the trend over time. Time in Status mainly allows you to see how much time each issue spent on each status or assigned to each assignee. You can combine statuses in any way into consolidated…

Hello @Lee Street You can have a look at Kanban Boards' Control Chart for that. It doesn't show individual issues but will give you an idea about the overall trend. You can also try creating custom fields to keep dates and use automation rules to populate those fields. Then you can make your own calculations. The downsides…

Thanks @Angélica Luz , I'll be watching the issue. EmreT

Hello @Dayanand For a ready-built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 assigned to each assignee. You can combine statuses…