Mehmet A _Bloompeak_ Atlassian Partner

Hi @Antoaneta Iskra If you need a lightweight, visual and user-centric capacity planning (individual capacity planning) experience, you can try Sprint Capacity Planner for Jira developed by our team. This app offers sprint capacity planning with an intuitive calendar interface. It enables you track user-level team…

Hi @Alice Blaese Managing capacity for distributed teams is tricky—especially when team members span different time zones, observe local national holidays or have varying working hours and availability. If you need a visual and user-centric capacity planning experience to handle these distributed teams, you can try Sprint…

Hi @Shravya Chinthapatla Managing individual user capacity directly inside standard Jira can be challenging. If you need a lightweight, visual and user-centric capacity planning experience directly on your board, check out Sprint Capacity Planner for Jira developed by our team. It specifically fills this gap by…

Hi @Sheen Kaul Welcome to the Atlassian Community! As far I know, it is not possible to show sum of QA and Dev story points on Jira board. If you prefer using a marketplace app, you can display "Sum of QA Story Points" and "Sum of Dev Story Points" on your Jira dashboard by using Sum Up Reports for Jira app developed by…

Hi @Julio Martinez Prieto Jira doesn't have a built-in solution for status transition acount. If you prefer using a marketplace app, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status. Here is the online demo link, you can see it in…

Hi @Pavan Thota iGTB Welcome to the Atlassian Community! Jira doesn't have a built-in solution for "time in status" info. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse. If you prefer using a…

Hi @LuckyLuke , You can try Reports - Charts and Graphs for Jira app developed by our team. For your specific requirement you can get a bar chart of sum of time spent by created(day, week or month) for each component as in the below screenshot. You can set X-axis created field granularity to day, week or month. Here is our…

Hi @Raunak Maskay Jira doesn't have a built-in solution for the reports you need. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse. If you prefer using a marketplace app, you can try Status Time…

Hi @anakaren.martinez Welcome to Atlassian Community! There is no built-in solution for the report you asked. If you prefer using a marketplace solution, you can try Project Roles- Groups and Users app. This app introduces a new tab to your projects named "Project Roles" and this page displays the project roles and the…

Hi @Mayur Gaikwad/Tech PMO The raw data you need is available in issue history and you can get it using Jira Rest API. The API returns a JSON response containing all status changes for each issue. You will need to parse this data to identify the timestamps for key status transitions. If you prefer using a marketplace app,…

Hi @[deleted] Yes, you use Status Time Reports Free. If you have any questions, feel free to schedule a call with us.

Hi @Jayanth , In theory, yes it is possible to exclude non-working hours, weekends and holidays from time spent in a status. But considering multiple national holidays in a year, daylight savings time changes, multiple cases for status start&exit dates(e.g. status entered within working hour but exited in non-working hour…

Hi @Eduardo Bentes Carneiro , You need to apply the below steps for each status you want to track. Below is an example for "In Progress" status. * Create a custom field named In Progress Start Time Choose the Date Time Picker field type. Our automation will use this field to store the time when the issue is transitioned to…

Another alternative might be using Sum Up Reports for Jira app developed by our team. It provides bottom line sum ups.

Hi @Eric Lynch , As @Danut M _StonikByte_ mentioned, you can achieve this using the built-in Two Dimensional Filter Statistics and Issue Statistics gadgets. But you need 3 different gadgets. If you're considering using a marketplace app, you can try the 'Reports - Charts and Graphs for Jira' app developed by our team. It…

Hi @tara wilding , As @Kris Dewachter mentioned you might be looking for one of the following two cases: Case #1: Tickets whose SLA was breached last month (e.g., tickets created in December but with SLA breaches in February Unfortunately, it is not possible to retrieve this data using JQL alone because Jira does not store…

Hi @Ashley Byrd Jira doesn't have a built-in solution for the report you mentioned. You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status. Here is the online demo link, you can see it in action and try without installing the app. For…

Hi @Ken Obsequio As you mentioned, the name of the built-in "Time To Resolve" field is a bit confusing and there is no direct way of getting time passed until resolution of the ticket in Jira Service Management. You either need automation rules or a marketplace app to get resolution time. If you prefer using a marketplace…

Hi @Philip Abdalla Welcome to the Atlassian Community! The data you are asking is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse to calculate the time passed in "Blocked" status. If you prefer using a marketplace app,…

Hi @Dhruti Shah There is no direct built-in solution to get time passed between statuses. You can use automation rules and custom fields to calculate it. An alternative is using a marketplace app. You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed…

Hi @Abhishek Ashok Dingre As far as I understand, what you are looking for is a cycle time (the time it takes for the team to start working on an issue and complete it) report. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning…

Hi @Naresh Rajak As far as I understand, what you are looking for is a cycle time (the time it takes for the team to start working on an issue and complete it) report. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json…

Hi @Farid H. Nia Jira doesn't have a built-in solution for status transition dates. If you prefer using a marketplace app, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status. Here is the online demo link, you can see it in action…

Hi @Myles Boyd There is no direct built-in solution to get time passed on "Open" status. You can use automation rules and custom fields to calculate your resolution time. If you prefer using a marketplace app one day, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on…

Hi @Arnelys Jira doesn't have a built-in solution for the report you mentioned. You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status. Here is the online demo link, you can see it in action and try without installing the app. For your…

Hi mohsen.nasiri@xentral.com Welcome to the Atlassian Community! As far as I understand, what you are looking for is a lead time (the time interval between the moment an issue is requested to the moment it is completed) report. The raw data you need is available in issue history and you can get it using Jira Rest API. It…

Hi @Learning123 , Yes, the data source of the chart can be any JQL. You can type your own JQL as in the screenshot below.

Hi @JJ Legelis , In Jira, there are 3 status categories: New, In Progress and Done. Each status is mapped to one of these 3 status categories. If the statuses "Blocked", "In Progress" and "Escalated" are mapped to the "In Progress" category in your workflow, then the JQL below might work. statusCategoryChangedDate <= -30d…

Hi @Learning123, If you prefer using a marketplace app, you can easily get BUG vs STORY ratio using Reports - Charts and Graphs for Jira app as can be seen in the screenshot below . It shows bug ratio trend by issue creation month. The app is super dynamic. Once you change X-axis from "Created(month)" to "Sprint", then you…

Hi @Sorokach, Mark D Welcome to the Atlassian Community! Cycle time and lead time raw data is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse to calculate cycle time and lead time. If you prefer using a marketplace app,…