Valeriia_Havrylenko_SaaSJet Atlassian Partner

@Calogero Bonasia Happy to help!

 Hi @Orkun Ovayurt 👋 Welcome to the Community! Unfortunately, native Jira JQL doesn’t support direct calculations between two date fields like created and resolved. JQL is great for filtering issues based on values, but it doesn’t perform arithmetic operations (like subtracting dates) out of the box. But here are a few…

Hi @Augu J N, If you're looking to calculate MTTR (Mean Time to Resolution) and populate a custom field automatically, there are a couple of approaches depending on the complexity and accuracy you need. 1. Using Jira Automation (Basic)Jira Automation can help you approximate MTTR by calculating the time between two status…

Hi @Nayyer Abdul Rab 👋 Out of the box, Jira doesn’t provide a dedicated product development dashboard that tracks the full journey from ideation through MVP launch. However, you can definitely build one with a combination of Jira features and Marketplace apps. Here’s how you could set it up: 1. Use Jira’s built-in…

Hi @Kevin Ryan 👋 Jira’s built-in reports (like Burndown or CFD) can feel restrictive since they often don’t let you customize filters or focus on specific statuses. Here are a few approaches you can take: 1. Use Jira filters with Dashboard gadgets Create JQL filters for your exact statuses or timeframes. Add gadgets like…

Hi @Édpo César 👋 Out of the box, Jira doesn’t provide this level of detail. SLA timers only cover status-based time tracking (and the feature request you linked is still open). However, here are a couple of approaches you can consider: 1. Marketplace Apps Tools like Time Metrics Tracker | Time Between Statuses (developed…

Hi @Hamsa Ranganathaiah 👋 The distinction between Cycle Time and Lead Time often causes confusion. Here’s how they are typically defined in Agile and in Jira reporting Lead Time Start point: When the issue is created (or added to the backlog, depending on your setup). End point: When the issue is completed/Done. What it…

@Morgan Watts Thanks, Morgan! Really appreciate the kind words 😊Totally get the restrictions around apps, if that ever changes, we’d love for you to give it a try. And yep, we’re all about making things simple and user-friendly. Thanks again!

Hi @Joshua Stokes 👋 Thanks for the question — and great summary from @Dave Rosenlund _Trundl_and @Trudy P Claspill 🙌 You're absolutely right: At the moment, all Jira Cloud apps (including Time in Status) are billed based on the total number of licensed users on your Jira instance — not just those who actively use the app.…

Hi @Prathima 👋 That's a great question — and you're very close to solving it already! To measure how many tickets a developer completed development within a given timeframe, you need to track status transitions, specifically when an issue moves from "Development" to "Testing". 🔹 Here’s how you can approach it: Use Time…

Hi @Saad Ahmad 👋 Great question — tracking status movement over time at the Epic level is key for analyzing workflow progress! While Jira’s built-in gadgets are limited in this regard, the Time In Status add-on can help you achieve exactly what you're looking for. 📊 Here’s how TIS can cover your needs: ✅ 1. Current vs.…

Hi @Moheb Hedayat 👋 Welcome to the Community! It depends on what kind of data you're looking to report on from more than one year back. Jira provides a variety of built-in reports, but most of them have limitations when it comes to historical data. For example: Control Chart and Cumulative Flow Diagram (used in Kanban…

Hi @Shaun McGuire 👋 I completely agree with what Bill Sheboy said — Jira doesn’t have a built-in field to calculate cumulative time in status, as it would require analyzing issue history. It’s a good idea to first check with your Jira Site Admin to see if your instance already has a Marketplace app installed for this…

Hi @Mic Streeter Welcome to the Community! Thanks for your question! 🙌 From the screenshot you shared, it looks like you're referring to the "Workload" section in the Time In Status Sprint Report. However, just to be sure, I recommend reaching out to our SaaSJet Support or email us at support@saasjet.atlassian.net, so they…

Hi @jim_taylor I'm Valeriia from SaaSJet, and I'm here to help! The Time to Resolution metric in Jira is typically measured in hours and minutes, but the specific format can depend on your Jira settings and the reporting tool you’re using. The value 332:11 suggests a large time value, which may not align with your…

Hi @mohd.zakir 👋 Welcome to the Atlassian community! If an app is an option for you, try Time In Status. Issue committed and completed data are available through Sprint Performance Report feature. Add-on developed by my team. Have a nice day and happy sprinting 🥳

Hi @MIke Killion 👋 Welcome to the Atlassian community! If an app from the Atlassian Marketplace is an option for you, try Time In Status. To track the dates that a Jira item's statuses changed just simply: * Choose the Status Entrance Date Report * Filter issues by created, updated, resolved and apply date and time ranges…

Hi @Marion Vandeputte Welcome to the Community! Your observation makes sense, and I’ve encountered similar cases before. The discrepancy between Resolution Time and Time Waiting on Customer is likely due to the way these metrics are calculated and how Jira gadgets process data. Possible reasons for the difference: * Time…

Hi @Sean Duffy 👋 If you consider using other add-ons, option for you can be Time in Status. You can get various real time reports with add-on. To get average time to resolve trend line on a bar chart just * Choose Average Time Report * Sort Item by Project (or Assignee, or JQL etc) * Filter issues based on your preferred…

Hi @[deleted] Welcome to the Community! Also if you are open to try a marketplace solution, Time in Status can be a great solution. Add-on provides detailed time tracking reports that help you analyze support performance. Here’s how you can set up the reports you need: 1. New Tickets Created Per Month – View All Year Use…

Hi @Dinonath Khan 👋 If you consider installing third-party add-ons, Time In Status сan be solution for you. 1. The usual Time in Status report. It shows you how long tasks were in each of the workflow statuses. 2. The Assignee time report will notify you of how much time each Assignee spent on each task. 3. Also you can…

Hi @Nicola J Also if you are open to try a marketplace solution, Time in Status can be a solution you. You can track the progress of a request and monitor how long it stays in each phase without creating a new issue type. Add-on allows you to see how long each issue has been in each status or column, providing detailed…

Hi @Rudy O. 👋 Welcome to the Community! If you're open to apps, Sprint Report from Time in Status can be a great solution. How Time in Status Sprint Report Can Help: * Multi-Sprint Analysis – View trends over the past 7 sprints to identify peaks and valleys in workload. * Tracks time spent in each status during the sprint…

Hello @Lauren Maguire 👋 Welcome to the Atlassian Community! Also if you are open to try a marketplace solution Time in Status can be a great solution. You can easily measure average age of the backlog items in your project backlog. For this just: * Choose Average Time Report * Filter by Project or JQL etc. * Filter issues…

Hi @[deleted] Also if you are open to try a marketplace solution, I recommend Time in Status can be a great solution. Add-on allows you to see how long each issue has been in each status or column, providing detailed reports on time in status, cycle time, and other key metrics. This can be especially helpful if you want a…

Hi @Konstantin Löscher 👋 Welcome to the Atlassian community! If an app from the Atlassian Marketplace is an option for you, try Time In Status. To extract the date of a specific status change from the history Just simply: * Choose the Status Entrance Date Report * Filter issues by created, updated, resolved and apply date…

Hi @Sarthak Solutions 👋 Welcome to the Community! If you're open to apps, Sprint Report from Time in Status can be a great solution. How Time in Status Sprint Report Can Help: * Multi-Sprint Analysis – View trends over the past 7 sprints to identify peaks and valleys in workload. * Tracks time spent in each status during…

Hi @Eric Lynch , Welcome to the Atlassian Community! If you don't mind looking at other apps, you can try Sprint Report from Time in Status app, which my team developed. The report gives Scrum teams a detailed overview of sprint activities and data. It’s an invaluable tool for tracking progress and performance from…

Hi @Ashley Byrd 👋 If you consider installing third-party add-ons, option for you can be Time In Status. You can get time spent in that status when issue is transitioned of one status for another one. Іdentify the loops in the workflow in a few clicks. Add-on developed by my team. I hope you find this helpful 🚀

Hi @Ashley Byrd 👋 If you consider installing third-party add-ons, option for you can be Time In Status. You can get various real time reports with add-on. Іdentify the loops in the workflow in a few clicks. For this just: * Choose Project, Assignee, Sprint etc. * Filter issues by Time Ranges * Enjoy you report as Table or…