Anastasiia Maliei SaaSJet Atlassian Partner

Jira gives you standard reports for flow metrics: the Control Chart (cycle time per work item, with average and rolling average) and the Cumulative Flow Diagram (WIP and growing queues by status). But both reports have limits and aren't very flexible: You can't group statuses into custom metrics like Lead Time, Cycle Time,…

On your point about “metrics that actually help me decide something” — I’d add Sprint Performance as a useful example. In our Sprint Performance Report from the Time in Status app by SaaSJet, we focus less on a single final score and more on the signals that help explain why a sprint went the way it did: Committed vs.…

Нi @Marcelo Montaño Sánchez You're absolutely right: the outcome is the point. A ticket closed inside SLA but with the customer still stuck isn't a win. The way I think about it: metrics aren't there to define good support — they're there to protect the part of the job that actually matters. If they can show me where…

If you want resolution time for every ticket individually rather than a single average, use a report grid — one that shows one row per issue with the duration calculated for each, not an aggregate. For this I'd recommend our app Time Metrics Tracker | Time Between Statuses. You create a Resolution Time metric: pick the…

@Yana Misiura_BrizoIT I'm really glad this article was helpful!

@Anwesha Pan Thank you very much!

Hi @Kim_Vencill, If you’re open to using a Marketplace app, this use case can be covered with Time Metrics Tracker. In the app, you can create a custom Cycle Time metric by selecting the start and end statuses of your workflow. Then you can run the report for a specific date range — for example, using the resolved date if…

Hi @Admin, A reliable way to handle this without scripting is to calculate time against a work schedule using a Marketplace app. I can recommended - Time Metrics Tracker | Time Between Statuses, you would approach your case like this: Create a metric that measures the time between Created and Resolution, or between the two…

Hi @Hansel Faren, Welcome to the Community! The examples you shared look more like a custom dashboard/mockup than a standard Jira dashboard, so it may be difficult to recreate the exact same view with native Jira gadgets only. If your goal is to get a clearer dashboard for workflow performance, bottlenecks, and task…

Hi , You can achieve this with Time Metrics Tracker | Time Between Statuses. The app lets you create your own custom time metric to calculate the time between specific status transitions. For example, you can create a metric like New → In Progress and configure it to start counting when an issue enters New and stop when it…

Hi, @BAL GOVIND YADAV For this use case, the best approach would be to use Time Metric Tracker instead of trying to calculate it manually with smart values in Jira Automation. You can create the required metric, for your example - Bug Resolution Time, and configure it to calculate the time from issue creation until…

Hi @sravani vennapusa! You can calculate this with the Time Metrics Tracker app. To do this, create a custom metric for bug age and exclude the statuses you don’t want to count — in your case, On hold. This will let you calculate the time from creation to closure without including the time the issue spent on hold. With…

Hi @Anser Ghazzaal Ali ! You can actually handle this with our app Time Metrics Tracker | Time Between Statuses It lets you calculate time spent in any status or between multiple statuses, and you can fully customize the metrics to match your workflow (cycle time, waiting time, time between specific steps — whatever you…

Hi, @Corinne Guibert Native Jira dashboard gadgets don’t provide a built-in way to calculate and display the average duration between release start date and release date. However, this can be covered with a Marketplace app like Time Metrics Tracker | Time Between Statuses. With the app, you can configure a custom duration…

Hi @joshalexandre Jira’s built-in Pull request cycle time metric is useful, but it’s quite limited if you want to zoom out and analyze the trend over longer periods. If your team reflects PR or code review work in Jira workflow statuses, Time Metric Trend Gadget can help with this. You can create a workflow-based metric…

If you’re open to third-party apps, one option to consider is Time Metrics Tracker (built by my team). It can be useful if you want to track open work as it ages, not only issues after they are resolved. For example, the WIP Run Chart helps show how long current in-progress issues have already been open, which can make it…

Hi, @Raheem Pillay What JSM shows there is usually SLA time, not just the full time from Created → Resolved. So if you’re seeing very low values like 0:01, that’s often because of things like: * the SLA starting later than ticket creation * pause conditions * business hours/calendar rules * or just the way the value is…

Hi @Mary Doherty! Welcome to the Atlassian Community. It’s a great question, and you’re definitely not alone in this — many teams find that getting a simple, clear list of cycle times can be surprisingly tricky in Jira. You can try using the Control Chart, but as you’ve noticed, it doesn’t always make it easy to see a…

Hi @Ashwin Kurundkar If you are looking for a straightforward way to get these timestamps and calculations, I recommend trying Time Metrics Tracker (developed by my team at SaaSJet). It was specifically designed to measure workflow connections and transition times. Here is how it can help with your specific request: -…

Hі @omid sh If you find that the calculation logic in Jira becomes too cumbersome or difficult to maintain, you might want to look at Time Metrics Tracker by SaaSJet. I’ve seen many teams switch to this tool when they hit limitations with standard reporting for business hour calculations. Here is why it fits your specific…

@Elena_Elevatic, thank you!

Hi @Suraj Pawar 1. Which Jira features are best for tracking progress? To keep it simple, focus on the core essentials: * Boards: This is your main workspace. For "simple and clear" tracking, a Kanban Board is best. It visualizes the flow of work using columns (e.g., To Do -> In Progress -> Done). You simply drag cards…

Hi @ckopanon I’d recommend using the Time Metrics Tracker | Time Between Statuses by SaaSJet app. It’s specifically designed to measure time-related metrics such as Resolution Time and average time, and it automatically calculates the arithmetic mean for you, so you don’t need to build complex reports manually. With this…

@Mustafa Mahdi Thank you for your feedback!

Hі, @Ron Sethman ! The issue you are facing is quite common. Standard Jira reports rely heavily on the Resolution Date, and if your team skips specific workflow steps, this field remains empty, causing your "Average Age" report to be inaccurate. Since manually fixing historical data is time-consuming, the most effective…

Hi @David Martínez López I understand you might be looking for a native solution or a workaround, but I’d like to suggest a tool that was developed exactly for this kind of request—to easily measure transition times and cycle times without complex setups. You might want to try Time Metrics Tracker: Time Between Statuses.…

Hi @Kevin Roe, If you're looking for ways to make time logging more consistent across the team, I recently wrote a short article with practical, real-world tips on building a strong time-tracking culture — it might be useful for your case: 👉 Five Practical Tips to Build a Strong Time-Tracking Culture

@Biswash Lamsal In Time & Cost Tracker, the app shows all existing Jira fields, including custom fields like Start Time / End Time if they exist in your Jira instance. So theoretically, you could include these fields in your report. If some fields don’t show any values initially, that can usually be fixed — for example, by…

Thanks for your question @Biswash Lamsal ! In Time & Cost Tracker, we currently track only the total time spent on a task — there aren’t separate Start Time and End Time fields. You can log the number of hours or minutes worked, and the app will calculate the total automatically. Regarding expenses, yes — you can record…

Hi @Biswash Lamsal 👋 I totally get your frustration - doing the same cleanup in Excel after every export can be exhausting. We actually built our app Time & Cost Tracker for Jira exactly to solve these kinds of reporting pains. Here’s how it helps: ✨ Log time directly on issues - with all the details you need. ✨ Customize…