Emre Toptancı [OBSS] Atlassian Partner

Hello @Supriya.Mandale , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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.…

Hello @Phil Bustin Jira does not offer this out-of-the-box, but the data needed for this report is available in each issue's history. The closest you can get out-of-the-box is the Control Chart that is available on Kanban Boards. Alternatively, you can get a cycle time report that is completely based on issue histories…

Hello @Mister Femi You can't do this with basic JQL but a marketplace app can help. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how much…

Hello @Prakhar Vedsa Things like discussions, conversations, rework, etc can happen at any stage of the flow. The only way to track these would be to make your team log work on issues about this. I don't recommend doing this because it probably won't give you trustworthy data anyway. But if you MUST see the times spent on…

Hello @Zarshah Rashid, I've got the perfect solution for you that will give more that what you asked for. Our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It can even give you times for block reasons. The app is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows…

Hello @Prakhar Vedsa , Mark's answer pretty much covers the important points but I would like to make some additions. 1- When working with sprints, the team concentrates on the sprint backlog and does whatever is needed to complete the sprint backlog. Many things run in parallel in such high-velocity environments. Lines…

Hello @Lee Street If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. You can…

Hello @dhernandezs This is not available as an OOTB feature. You can try implementing this yourself or use a ready marketplace app for this. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data…

Hello @Parveen Taj, If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. The…

Hello @Sunil Bharadwaj , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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.…

Hello @samuel.t , I think I can offer you something that will meet your needs and even more. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for these needs. It is available for Jira Server, Cloud, and Data Center. Time in Status mainly allows you to see how…

Hello @Claire Lowry-Hubball , As others have pointed out, this is not available as an OOTB feature. You can try implementing this yourself or use a ready marketplace app for this. (The definition of a reasonable price is in the eye of the customer so I will leave that part to you.) If you are OK with using a marketplace…

Hello Vereesh, For calculating the age of each individual defect, you can use Status Duration (with Consolidated Column feature) or Duration Between Statuses report types of Time in status. (These are separate report types and currently there is no way to get multiple report types in a single report.) And about group time:…

Hello @Porush Verma , If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. 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. The app has Consolidated…

Hello @Veeresh , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. In…

Hello @Kyra Mayock , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. The…

Hello @Chilakala Sai Bharadwaj If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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…

Hello @Kamal Rajpal , If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. 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. The app has Consolidated…

Hello @Penry John If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. The app…

Hello @Tata Tatkhashvili If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this need. Time in Status provides a much more detailed, transparent, and flexible solution compared to the standard Control Chart. It is available for Jira Server, Cloud, and Data…

Hello @Jordon Martig , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this need. 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. The app…

Hello @Neha Panchal , Our team at OBSS built Timepiece - Time in Status for Jira for this exact need. You can use Time in Status to get these reports in Jira or use the app's REST API to pull the calculated values to a BI platform. Time in Status mainly allows you to see how much time each issue spent on each status and on…

Hello @Vinay Vira, I suggest you use our marketplace app Timepiece - Time in Status for Jira for this which can give you these numbers out-of-the-box without the need to write any calculation code. You can use the REST API provided by our app to pull calculated data into easyBI. Time in Status mainly allows you to see how…

Hello @Dean Kadar , If you go to "Scrum Board Settings >> Estimation >> Time Tracking" and select "Remaining Estimate and Time Spent ", then your Burndown Chart will be able to show progress for non-finished stories (provided that you enter Original Estimate and Remaining Estimate values on your stories). Velocity Chart on…

Hello @Ryan Wolfe , Introducing another initial status into your workflow is the correct approach. By doing that, you can distinguish the issues that are waiting for their turn and those that are actually being worked on. There are two built-in Jira reports for this need. The Average Age Report/Chart and the Resolution…

Hello @Raghu , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center. You can use this solution for all projects and boards. Time in Status mainly allows you to see how much time each issue…

Hello @Sean , If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. 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. The app has…

Hi Tata, Why the restriction? I don't know. I guess because Atlassian chose to do it that way. If you are using a Kanban Board, you should already have this report. If you are using a Scrum Board, there is no way to add this report to a Scrum board. Creating a new board is not much of a problem. Just create a new Kanban…

Hi Tata, Control Chart is available as a Kanban Board report. If you create a new Kanban board you will find Control Charts in the Reports section of that board. EmreT

Hello @Porush Verma , To get the issues that were in Reopened status in the past but that are currently closed, you can use the following JQL query. status was Reopened and Status = Closed To get how many times the issues were reopened, you will need to use a marketplace app. Our team at OBSS built Timepiece - Time in…