Khrystyna_Dzhus_SaaSJet_ Atlassian Partner

Hi @Abhishek P, The native options suggested above are a good starting point: Days in column helps flag aging work on the board, while saved filters and scheduled automation can bring work items needing attention to your team’s notice. Jira records status changes in work item history, but getting a report of time spent in…

Hi @Tomas Greif, The Updated field will always drift for this reason. What you need is the status change history, which Jira doesn’t expose as a sortable column natively. If you’re open to a Marketplace app, Time in Status by SaaSJet handles this, and it works with Jira Product Discovery ideas: Open the Status Entrance…

Hi @Anuj Batta If resolving everything from a team label becomes difficult with a custom Rovo setup, there is also a ready-made option you could try. Time in Status by SaaSJet includes a Sprint Report Insights Rovo agent that automatically generates a retrospective based on sprint data — completion rate, velocity, scope…

Hi @Maggie Rhoads Jira Cloud’s native Velocity Report doesn’t currently let you set a custom date range for the chart. If your goal is to focus on a smaller part of your sprint history, Time in Status by SaaSJet offers another approach through the Sprint Performance Report. You can select a specific completed sprint (from…

Hi @Helmut Priyanka Just to clarify the use case: what exactly would these duration fields represent? Do users need to manually enter values such as 1d 23h 12m or 50:30, or are you trying to track how long a work item spends in particular workflow statuses? If you need users to enter the duration manually, then you would…

Hi @Shailesh Yadav , If you are using a company-managed Jira project and the report does not need to be added to a dashboard, Jira may already provide this natively. Go to: Project/Space → Reports → Work item creation trend This built-in report shows the number of work items created over time and splits the columns by…

Thanks @Lukasz Modzelewski ! So glad to learn and grow alongside such a supportive community.

Hi @Kristy , Since you're on Kanban without sprints, native sprint-based burndown gadgets won't apply. But there are a couple of ways to get this with Time in Status by SaaSJet. Time trend analysis: Add the Burndown Status Tracker gadget to your dashboard. It's configured with Space, Work item types, Statuses, and a Time…

Hi @Williams_ Dave, In Jira, you can use the Created and Resolved fields to see when a ticket was opened and resolved. Jira does not have a separate standard Date completed field, and for resolved tickets, the time the ticket was open is the difference between the Created and Resolved dates. For more detailed…

Hi @Chris Berry, As mentioned, there's no velocity figure on the Backlog screen itself; historical velocity is in the Velocity Report under the Reports tab. That part won't change without a feature request to Atlassian. The thing you're actually after — tracking velocity over time — is where the native Velocity Report…

Hi @Kim_Vencill , If you're open to a Marketplace app, this is exactly what Time in Status can do — and it can give you the single average number, not just a chart. For the ADO-style KPI: 1. In Columns → Status Groups, create a group called "Cycle Time" and add the statuses that represent your delivery phase (e.g. In…

Hi @Enrique BESUMAN BARCENAS Great question — this "bounce back to Open" pattern is one of the clearest signals of hidden rework, and native Jira won't count status re-entries for you without custom automation or manually digging through each issue's history. The quickest way to get this exact metric is a Marketplace app.…

Hi @sravani vennapusa, If you need to capture the date when an issue entered a specific status, you could try the Time in Status app. It has a dedicated Status Entrance Date report designed for exactly this use case. You can also apply column filters to narrow results by a particular status entrance date. Disclaimer: I’m…

Hi @송지현 , If you are open to trying a marketplace app, I can suggest the Accurate Time in Status gadget developed by the Time in Status app by SaaSJet. After you install the app, find Accurate Time in Status (by SaaSJet) in the search results and add it. In the gadget settings, select the project you need, and you will see…

Hi @scott_norris , I can suggest trying the Sprint Report feature in the Time in Status app by SaaSJet (developed by my team). It helps you track your team’s progress based on the estimation method used on your board, such as Story Points, Work Item Count, or Original Time. In addition to team velocity, you can see…

Hi @Harry Foreman You’re absolutely right — this is one of the most common gaps in Jira. There’s no native way to track time in status per issue. Jira focuses more on workflow tracking than time analytics. So if you need to measure how long an issue actually spends in each status, you’ll need a Marketplace app. For…

Hi @Soma Rohit Yes, you are right. In Jira Cloud, the “age” is usually calculated only after the issue is resolved. Therefore, it is not very helpful for tracking ongoing work. If you need to see the running age of an issue while it’s still open, this usually requires using a third-party application. For example, the Time…

Hi @PLaksh11 , This is very difficult to do using standard Jira tools (you need to create a bunch of complex automation rules and additional fields). I suggest trying the marketplace add-on Time in Status by SaaSJet (developed by my team), which can help with your use case. It provides an Average Time report that shows the…

Hey @Placid Cardoz, Jira stores this data in the changelog, but as you may have noticed, it is not available through standard data exports. Therefore, attempts to analyze “queue bouncing” in Sheets usually do not yield meaningful results. For this specific use case (when tickets jump between queues), it is most effective…

Hi @Amit Singh , If you use Scrum boards, the native Jira sprint report provides a good overview of sprint progress. To understand the workload distribution among team members, you can create a JQL query and use it as the data source for dashboard gadgets such as "Two Dimensional Statistics - Assignee × Status" or "Pie…

Hi @mr john , It is definitely time-consuming to manually calculate the time spent in each status from the issue history. Unfortunately, Jira does not provide a built-in feature or native report to calculate the total time spent in each status per issue. You can set up some automation, but it will still be limited. Because…

I personally realized that I had a rather narrow understanding of Jira’s functionality and Atlassian as a whole 🙂 My first impression was how impressively feature-rich Atlassian is and how many useful tools it offers, even though not all of them were immediately clear to me. The Jira and Confluence courses were very…

Thank you!:)

Thank you!

Great article! Thanks for sharing valuable info

Thanks for sharing these insights!

Thanks for sharing valuable info!

Thanks for the valuable info!

Hi! For me, the most convenient SEO tool is Semrush. It has all the necessary functions for keyword analysis, position tracking, site audit, AI visibility tracking, and competitor research. Hovewer, it does not give a complete picture of an SEO audit. I also use Ahrefs to find errors, such as 404 pages and broken links.…

In my experience, we tested the results of articles that were completely generated by AI and those that were generated with 70-80% AI and 20-30% human input. According to this research, most articles that were 100% generated by AI did not drive any traffic. I believe that AI tools can and should be used, but wisely, and it…