Ayça Erdem_OBSS_ Atlassian Partner

Hello @Sharon G_ There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. 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 a report type that…

Hello @Shaun McGuire There is no built-in field in Jira that calculates Time in Status, and we also don’t have a custom field for that. Jira simply doesn’t track this data in a way that’s accessible without additional tooling. However, if you're looking to report on how long issues spend in each status, I highly recommend…

 Hi Emilia, Great question! Jira doesn’t automatically recalculate SLA metrics for past issues when you change the SLA definition, but with Timepiece - Time in Status for Jira developed by my team at OBSS, you can still generate historical reports based on your updated criteria. Our app allows you to analyze SLA-related…

Hello @MIke Killion Welcome to the community The data you need is stored in Jira's issue history, but Jira doesn’t provide a built-in way to extract it into a structured report automatically. Manually digging through issue histories is time-consuming and errors. That's where Timepiece - Time in Status for Jira, developed…

Hello @jeroen_wilmes I’d like to introduce you to Timepiece - Time in Status for Jira, developed by my team at OBSS. It is available for both Jira Cloud and Data Center. If you're looking for a way to track how many times issues have transitioned into specific statuses , Timepiece offers an advanced Status Count Report…

Hello @Sarah Crown Jira's built-in dashboard charts do not support overlaying an average time to resolve trend line on a bar chart. However, you can achieve this using Timepiece - Time in Status for Jira developed by my team at OBSS. Status Duration Report in Timepiece With Timepiece, you can: Generate a bar chart showing…

Hello @Dinonath Khan In Jira Service Management, you can check the History tab of an issue to see past assignees, but Jira's Assignee field only displays the current user assigned to the ticket. If you need to generate a report that includes all past assignees and the time they spent on each issue, you can use Timepiece -…

Hello @Konstantin Löscher An issue's status transitions are recorded in its history, which you can view directly from the issue screen in Jira or retrieve programmatically using Jira's REST API. Another solution is Timepiece - Time in Status for Jira , the oldest and leading Time in Status app in Atlassian…

Hello @[deleted] There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. 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 a report type that…

Hello @Ashley Byrd There is no built-in solution in Jira to automatically track time spent on epics and stories without manual time tracking. However, you can achieve this using a Marketplace app. Timepiece - Time in Status for Jira, developed by my team at OBSS, is the leading "Time in Status" app in the Atlassian…

Hello @Eduardo Bentes Carneiro You can achieve this with Jira Automation, but setting it up to measure time spent in each status would require complex configurations, development, testing, and ongoing maintenance making it quite costly. Using an app is a much more efficient and cost-effective solution since the necessary…

Hello mohsen.nasiri@xentral.com Welcome to the community. You can use Rich Filters to create calculated fields and visualize key metrics like average resolution time over time. With its time series gadget and filtering options, you can track trends and analyze performance based on different time frames. However, if you…

Hello @Randy O'Neal There is no built-in solution in Jira that allows you to override the original start date for a status transition. Jira tracks status durations based on historical issue transitions, and unfortunately, it does not provide an option to modify these timestamps. However, to get an accurate view of how long…

Hello @Akash Welcome to the community Unfortunately, Jira's own SLA counters do not work backward. Whenever an SLA is enabled, it starts calculating for issues that are within the SLA counter limits at that time. It does not calculate for issues whose SLA definition endpoint has been reached. To see historical SLA…

Hello @Leslie Barrett Keeping track of unresolved FixVersions that have been inactive for a long time can be tricky, but there are ways to streamline this process. You can approach this challenge in two ways: Option 1: Manual Filtering with JQL A quick way to filter FixVersions based on your criteria is to create a JQL…

Hi @Valentin Cardozo Jira provides various reports to analyze sprint productivity, but for tracking individual user productivity in detail, you might need a more tailored solution. If you are looking to analyze task resolution vs. estimated work and track historical progress, a good option is to use the Assignee-Based…

Hello @Archana You're right,Jira’s built-in filters and reports don’t provide a breakdown of logged work per user daily for each task. Here are two ways you can achieve this: Export Jira Worklogs to Excel Since you're looking for a solution without plugins, one option is to export Jira worklogs to Excel and use Pivot…

Hello @GCushnahan Welcome to the community You're right. Jira’s default export includes Created and Resolved Dates but doesn't track time spent in each status. For single issues, you can check the History tab under "Activity" to find timestamps for status changes, but this is impractical for large datasets. A simpler…

You're absolutely right! Jira’s default workload pie dashboard does not include spent time from sub-tasks, and automation rules can only do so much when it comes to aggregating time-tracking data. Since your rule successfully sums the original estimate from sub-tasks to the parent but doesn’t work the same way for spent…

@Kaladin Stormblessed Thanks for your question! Unfortunately, we don’t have Jira Automation enabled in our instance, so we're unable to set up this kind of rule. Do you have any alternative suggestions that might work without automation?

Hello @Myles Boyd Here are some solutions that you need; * Jira Automation & Custom Fields * You can set up Jira Automation to log timestamps when an issue enters or exits specific statuses (e.g., Open, Pending, Resolved). * Then, using a calculated custom field, you can determine the actual time spent in “active”…

 Hello @Farid H. Nia Welcome to the community! There are a few ways to solve this,check out the details below * Using JQL for Status Changes (Basic Query Approach) You can use JQL to find when a user story moved from "To Do" to "In Progress" and was later completed within a specific timeframe, such as January. * To find…

Hello @tara wilding If you need a JQL query to find issues where Time to First Response or Time to Resolution SLA has breached in the last month, you can use: ("Time to First Response" = breached() AND "Time to First Response" >= startOfMonth()) OR ("Time to Resolution" = breached() AND "Time to Resolution" >=…

Hello @Arnelys Welcome to the community Jira’s Workload Pie Chart does not include subtask time by default, but there are a few ways to achieve this: 1. Using Jira's Built-in Reports (Limited Approach) * You can use the Time Tracking Report, which includes both parent and subtask work logs. However, this report is not…

Hello @Abhishek Ashok Dingre Welcome to the community! JQL alone cannot calculate the time spent between two statuses. However, you have a few options to achieve this in Jira: 1. Using Jira’s Control Chart (Native Option) Jira’s Control Chart (available in Kanban boards) can help visualize how long issues took to move…

Hello @Kaladin Stormblessed@Kaladin Stormblessed Your challenge is a common one in workflows where multiple assignees contribute to the same issue at different stages. While simplifying your workflow to To Do, In Progress, and Done and using sub-tasks for individual responsibilities is one way to track ownership, it might…

Hi @Naresh Rajak Welcome to the community An issue’s status changes are logged in its issue history, which can be accessed from the issue view in Jira or through Jira’s REST API. While it’s possible to track and calculate the number of days an issue has been in a specific status manually, this process can be quite tedious…

Hello @Eric Lynch Welcome to the community The table you shared makes perfect sense—you’re trying to track how tickets progress through various stages during a sprint, but Jira’s Burndown Chart only reflects when an issue reaches a resolved status or the last column on the board. Since Jira's board columns are mainly for…

Hi @Ken Obsequio In Jira Service Management, "Time to Resolve" in SLA reports does not represent how long it took to resolve an issue. Instead, it typically shows the SLA target—the expected time a issue should be resolved. Similarly, "Time Remaining" refers to the countdown before a ticket breaches the SLA threshold. This…

Hello @Philip Abdalla Welcome to the community You can track how long each ticket has been blocked by checking when it last transitioned into the Blocked status. One way to do this programmatically is by retrieving issue history through the Jira REST API and extracting the timestamp of the latest status transition. This…