Gizem Gökçe (OBSS) Atlassian Partner

Hello @Xenia Chilkowich , When you say “sprint burndown based on Original Estimate,” do you mean tracking the remaining estimated work over the course of the sprint, using the issues’ Original Estimate as the initial value? Or would you like to track the sum of Original Estimate values assigned to each assignee over time?

Helle @Vando Goncalves _e-Core_ , Great question, and nice work building the average resolution time calculation in Atlassian Analytics. Unfortunately, Atlassian Analytics does not currently provide a native way to calculate time differences based on business hours or custom working calendars. All date difference…

Hello @jira_admin_cu , Trying to make this work with automation rules or scripts can quickly turn into a complex, high-maintenance setup — and even then, it often won’t handle existing issues the way you need. If you are open using a 3rd party app, we built Field Sync exactly for this kind of scenario. It can automatically…

Hello @Pedro Webster , If you’d like to report on issues that were flagged at any point in time — not just those currently flagged — you can achieve this using Timepiece – Time in Status for Jira, developed by my teams at OBSS, with the following reports: Any Field Duration Report This report shows how long each issue had…

Hello @Mayur Gaikwad/Tech PMO , The required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Good news that report is available in our application where you can directly learn the transition dates without having to deal with Jira issue histories. The app…

Hello @Davide Schillaci , We ran into a similar situation at my previous company. Beyond just the system limitations, our developers often forgot to log time, or entered inaccurate worklogs, so the native Time Spent field became unreliable for tracking actual effort. As a workaround, we shifted to measuring how long each…

Hello @Dinonath Khan , You can track the time each assignee spends in different workflow statuses using Timepiece - Time in Status for Jira. The Assignee Duration per Status report will provide a clear breakdown of how long each assignee spent time in each status. This will help you see, for example, how much time Assignee…

You could create a custom field within your Service Requests and have agents update it at each phase of the request, treating it like a status. This approach would allow you to track the progress of requests more easily. Additionally, our product, Timepiece, offers a report type called Any Field Duration. This report can…

Hello @[deleted] , Welcome to the community It sounds like you're looking for a more efficient and insightful way to track key metrics for your Jira Service Management system. Timepiece - Time in Status for Jira can help you easily generate the reports you need with clear and actionable views. Here's how Timepiece can…

Hello @Nicola J , If you're open to using a third-party app, your request is already covered. You can track the progress of your request and measure how long it stays in each phase using Timepiece - Time in Status for Jira. The Status Duration report shows how much time an issue spends in each status, giving your senior…

Hello @Lauren Maguire , Welcome to the community! You can easily get the average age of backlog items using Timepiece - Time in Status for Jira. Duration Between Statuses report lets you track how long each issue has been open by measuring the time from creation to today. By filtering for backlog items and enabling the…

Hello @paige.humbert , Welcome to the community! Unfortunately, Jira's SLA counters don't work backwards. They start tracking only when an SLA is enabled and won't calculate for issues that are already resolved. That's why you don't see a Breached alert for your closed service requests. The Time to First Response wasn't…

Hello @Jayanth , Yes, it is possible to calculate time in status using Jira Automation, but setting it up requires significant effort. You'll need to create multiple rules to track status entry/exit times, calculate time differences, and handle edge cases like weekends and non-working hours. Maintaining these rules over…

Hello @Nguyen Le Thanh_Candylio , Welcome to the community! In order to track the time spent by each assignee I suggest you use Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has several report types that will meet your need.…

Hello @Kevin Rowe , Welcome to the community! Are you looking for a way to calculate this directly in your BI tool, or would you consider using a ready-to-go report with a third-party app like Timepiece - Time in Status for Jira? Timepiece, which is built by my team at OBSS, provides a Duration Between Statuses report that…

Hello @Digvijay Singh Gehlot , You can use JQL to find issues that have been in the same status for a specific time range. Here’s how you can do it: JQL Query: To find issues that have been in the status "X" for more 90 days, you can use: <span>status</span> = <span>"X"</span> AND statusChangedDate >= <span>-90</span>dThis…

Hello @mateus.oliveira , The required data, which is the first transition date to status Done, is available in each issue's history. However, extracting it manually requires building a custom solution. A simpler approach is to use a Marketplace app that provides ready-to-use reports. Good news that report is available in…

@Dilan Koyunoğlu Hanım Merhabalar, Atlassian Community'e hoş geldiniz! This is not possible with native Jira capabilities, as Jira does not provide built-in tracking for business hours when calculating time between issue statuses. However, you can achieve this with Timepiece - Time in Status for Jira ,the oldest and…

Hello @Jstenger , Welcome to the community! "Average Time in Status (days)" represents the average duration issues spend in a specific status. The pink line could indicate trends or benchmarks for a particular status, as shown in the chart legend. If you're looking for more advanced and precise reporting, I recommend…

Hello @Pappu Saha , Welcome to the community! To measure team performance, work efficiency, time consumption, and productivity effectively across multiple Jira projects, if you are open to use 3rd party apps, I’d like to recommend Timepiece - Time in Status for Jira, which is developed by my team at OBSS. This app can…

Hello @Natalie Keane , If you're looking for a way to track time within Jira, I recommend Timepiece - Time in Status for Jira, which is developed by my team at OBSS. It offers comprehensive reports that will allow you to track time spent in different statuses and evaluate the efficiency of your workflow. Status Duration &…

Hello @andrejkovicovar , Welcome to the Community! The dots on cards are a visualization of how many days the card has been in the column. Hovering over the dots will provide you with the exact number of days the issue has spent in that column(status). However, this method involves manual effort and isn’t ideal for…

Hello @shay ron , Welcome to the community! As you've already mentioned, the required data is available in each issue's history but you will need to use a marketplace app to get ready-to-go reports. Good news that report is available in our application where you can directly learn the transition dates without having to…

Hello @Kashif Rahman , The JQL query you provided doesn’t yield the expected results because the timespentfield represents the total logged work time, not the actual time an issue spent between its creation and resolution. Unfortunately, Jira’s native JQL doesn’t support date arithmetic or calculations like determining the…

Hello @Learning123 , Unfortunately, Jira's default gadgets do not support the type of detailed ratio analysis you're describing, and I'm not familiar with the specifics of the Rich Filters plugin either. However, if you're open to using a third-party app, I highly recommend Timepiece - Time in Status for Jira, developed by…

Hello @JJ Legelis , Welcome to the community! Jira's native JQL has limitations when it comes to calculating dynamic durations, such as determining if an incident took more than "x days" to close. However, if you're open to using a third-party app, I highly recommend Timepiece - Time in Status for Jira, developed by my…

Hello @Sorokach, Mark D , Welcome to the community! For the metrics you're looking to review—such as Average User Story Cycle Time, Epic Lead Time, Average Velocity, and User Story Throughput—you can use a 3rd party reporting tool such as Timepiece - Time in Status for Jira , developed by my team, to generate these…

Hello @Alicia Redden , Welcome to the community! To show Assignee, Ticket Description, Status, and Days in Progress (or similar metrics) for all tickets assigned to specific Parent/Epics, you can use the Status Duration Report in Timepiece - Time in Status for Jira. Timepiece is a third-party app developed by our team at…

Hello @Safa Al Shuaili , Welcome to the community! If you're looking to extract the duration of each status based on working days, Timepiece - Time in Status for Jira is an excellent solution. Plus, it integrates with eazyBI, making it easier to visualize and analyze your data. Timepiece is developed by my team at OBSS and…

Hello @Celina Kim , Unfortunately, excluding weekends directly using JQL is not possible with the built-in features. However, you can achieve this with Timepiece – Time in Status for Jira,developed by my team at OBSS. Timepiece offers advanced reporting capabilities, including custom calendars that allow you to exclude…