Iryna Menzheha_SaaSJet Atlassian Partner

@Bill Sheboy Oh that’s super helpful! Great starting point for me. Appreciate such a detailed explanation. 

Thanks! Are you evaluating it on a sprint basis, or do you also perform monthly analyses? Do you use something else apart from board? I was told that having a WIP chart with some trendline in my Jira dashboard might be a good thing to monitor for me. But I mostly use a project board and see progress there. 

Hi @Julio Martinez Prieto You're looking to track how many times a developer moves an issue back and forth between "In Progress" - "Under Review" — a common situation during code review iterations. Native Jira Limitations Unfortunately, Jira's native JQL cannot count the number of status transitions. It only shows if a…

Hi @Pavan Thota iGTB 👋Welcome to the Atlassian Community! To get the ageing of a Jira defect based on status (e.g., how long it stayed in “Resolved”), here are your options: 1. Native Jira (Manual Method) Jira doesn't provide built-in status-duration reports. But you can check manually: Open the issue. Go to the History…

Hi @Ramesh Krishnan 👋 You're absolutely right — Control Chart is not available as a native Dashboard Gadget in Jira Cloud. Atlassian hasn’t yet made Control Chart directly embeddable on dashboards. ✅ Workaround Options: 🔹 1. Time in Status If you're open to solutions, Time in Status offers: A Chart View with a similar…

Hi @Ramesh Krishnan 👋 Unfortunately, native Jira reports like the Velocity Chart, Burndown, Burnup, and Control Chart are limited to boards (which are usually project- or team-specific), and don’t support direct filtering by Teams (from Advanced Roadmaps) across multiple projects. ✅ Workaround Using Solution – Time in…

Hello @Ajay thirth 👋 Welcome to the community! Hi @Ajay Thirth Welcome to the Atlassian Community! If you're open to exploring marketplace solutions, I’d love to introduce you to the app my team and I are working on — Time in Status For your exact need, we offer two helpful reports: Status Count report or Transition Count…

Hi @Phil 👋 Great question — while Jira's native JQL doesn’t allow dynamic calculations like "Current Date - Created Date" to display a ticket’s age in the filter results, there are two great workarounds using solutions (developed by my team) that make this super easy: 1. Time in Status With Time in Status, you can: See how…

Hi @Hunter Wessinger 👋 You're absolutely right to question the inconsistencies — Jira’s built-in SLA reporting in Service Management can sometimes show: Duplicates for tickets that were updated or recalculated across multiple days Issues as “breached” due to older SLA cycles (e.g., previously breached goals that were later…

Hi @Aditya Sinha ! 👋 Welcome to the Community! Great and detailed question — and you're absolutely right: retrieving status transition history at scale using the standard Jira REST API can become very inefficient due to the one-issue-per-request limit with changelogs. Let me break down your questions and provide…

 Hi @Mayur Gaikwad/Tech PMO 👋 Yes — Jira provides an API to retrieve status transition data, but not directly as "time in status" values. Instead, you can use the issue changelog from the Jira REST API to calculate time spent in each status manually. ✅ Jira REST API for Status Transitions You can use the following…

Hi @Raunak Maskay 👋 You’ve laid out a very clear and practical goal — tracking time spent in each swimlane/status, turnaround time, and SLA compliance in Jira Software. Let’s break it down by your questions: 1. Can you track SLA/time data in Jira Software (Standard Jira)? Yes, but it requires workarounds — since Jira…

Hi @Simon Jackson 👋 You're right — Jira’s native Sprint Insights don’t always work well when your team uses sub-tasks, since those aren’t always counted in velocity or progress calculations unless configured very specifically. If the insight report isn’t updating correctly, especially with subtasks, you might find it…

Hi @Nicola Biagi 👋 Welcome to the Community You're right: Jira allows only one assignee per task, but that doesn’t mean you can’t track contributions from multiple team members. And more importantly, if your goal is to manage team activities effectively, tracking who worked on what, for how long, and where the bottlenecks…

Hi @Bhuvaneswari Vasudevan 👋 If you’re looking to track how much time is spent on product discovery ideas in a JPD project, but don’t want your product managers to manually log hours — here’s a helpful workaround. Use Time in Status as a workaround (no time logging required) The app automatically calculates how long each…

Hi @ranjanajindal! You can achieve this in two ways — first, using Jira Automation, and second, with the Time Metrics Tracker | Time Between Statuses app if you’re looking for a no-code, ready-to-use approach. ✅ Native Jira Automation (Manual Configuration) To calculate Resolution Time excluding statuses like “On Hold,”…

Hi @Claire Abt 👋 Welcome to the Community! You're absolutely right — manually pulling transition timestamps from issue history is time-consuming (especially with back-and-forth status changes like “Input Required”). Option: Time In Status This app is great for exactly what you're looking for — it gives a detailed breakdown…

Hi @Preetham Bhat 👋 Great question — if you're looking to export story points data across multiple sprints and projects, including completed, not completed, added, and removed issues, here are your options: ✅ 1. Jira REST API (Best for Automation via Cron) You can use the Jira Agile REST API to fetch sprint-level data: Key…

Hi @Kevin Gilchrist 👋 Unfortunately, there’s no built-in gadget that lets you create a true scatter plot with individual issue dots and a custom metric like Cycle Time or Resolution Time — with creation date on the X-axis. If you open to apps, Scatter Plot Dashboard Gadget by Time Metrics Tracker Here’s what it looks like…

Hi @Gayatri.Chabbi 👋 Welcome to the Community ! If you're trying to download current sprint data (like completed/incomplete issues, story points, etc.) but can’t locate the Sprint Report, here’s what you can try: ✅ 1. How to Find the Sprint Report Go to your Scrum board in Jira Click Reports (left-hand menu) Select Sprint…

Hi @Sandeep Gowda 👋 Welcome to the Community! Let’s break this down. What you’re seeing: The “Sprint Commitment” insight compares: The total committed time in your current sprint (e.g., 2064h 38m), With the average time spent in past 5 sprints (17h 24m). That huge gap likely means: Too many issues were added to the sprint…

Hi @Alison Files 👋 If you ever need more flexibility with SLA reporting in the future, you might want to explore Time Metrics Tracker. With Time Metrics Tracker, you can: Measure the exact time between key status transitions like "Created" ➔ "Resolved" Filter out escalated or long-open tickets (e.g., those over 90 days)…

Hi and great question @Amy Chamberlain The calculation of Cycle Time and Lead Time indeed requires flexibility to adapt to varying workflow designs, and simplistic assumptions often fail to capture the nuances of real-world processes. For this need my team developed Time Metrics Tracker | Time Between Statuses If your…

Hi @George Mazurkiewicz 👋 Welcome to the Atlassian Community! You're on the right track using individual filters + pie charts per person! It works, but as you’ve noticed — it can get repetitive and hard to scale as your team grows. Here are a few alternatives that might simplify things: ✅ 1. Use a “Two-Dimensional Filter…

Hi @Suriya Kumar Sivasubramania 👋 Welcome to the Community! You're on the right track — having a consistent Sprint Status: Planned vs Actual report is one of the best ways to evaluate sprint health, team performance, and uncover improvement areas. Here's how you can approach this using Jira's built-in features and advanced…

Hi @Brian Allen 👋 Welcome to the Community! Thanks for your question — you’re absolutely right that milestones are currently visualized on the Roadmap using color-coded stars. This provides a good high-level view, but I agree it can be limiting if you're looking to generate detailed reports on milestone progress. At the…

Hi everyone 👋Just wanted to share that the Scatter Plot is now also available in the Time Metrics Tracker With this gadget, you can: Spot outliers Track issue completion over time Optimize team performance Give it a try if you're looking for more flexible reporting inside your Jira dashboards. Happy to answer any…

Hi @Eran Roiter ! 👋 You're raising a very relevant point — tracking quarterly progress across epics, story points, and sprints can be hard to manage manually, especially at scale. Jira’s native velocity and sprint reports are limited when it comes to longer timeframes like quarters and don’t offer the flexibility needed to…

Hi @Jesse Allen ! 👋 Welcome to the Community! While Jira’s native Sprint Report offers a high-level view, it doesn’t break things down by individual user. You might want to check out the Sprint Report from Time in Status. Here’s what you’ll get in the Sprint Report: 📊 Workload per assignee View how much work…

Hi @Miriam Grühn! 👋 Great questions — you’re absolutely on the right track wanting to measure only the time your team is actively working on tasks, and not the full lifetime of the ticket. Jira’s native Kanban reports (like Control Chart) provide some insights, but they’re limited when it comes to customization based on…