Iryna Komarnitska_SaaSJet_ Community Champion

Hi @sunil Kumar BV , If you're open to using a marketplace app, I can recommend one developed by my team. Time in Status app has several built-in reports that can help you. One of them is Status Entrance Date, which shows the date and time when the task was transferred to it. Another is the basic Time in Status report,…

Hi @Maxime Besson , I was intrigued by your use case and recreated it in our Time in Status app, which supports a flexible Pivot configuration. Could this setup work for you? How I configured it Select scope Project: chosen project Filter: issues updated in the last 30 days Set Pivot rows (in this order): Status → Sprint →…

Hi @Dima Kiselev , For a fair view of team performance, select reports that answer specific questions. If you’re open to Marketplace apps, my team builds Time in Status —it reads your workflow history (no timers) and turns it into the metrics managers actually use. Where does time really go? Use Time in Status (with Status…

Hi @Chasovskikh Kirill Although the app my team developed can't cover all your requests, it might still be helpful to you. Our team at SaaSJet developed the Time in Status app, which includes a Sprint Report that gives a visual breakdown of key sprint metrics. The report provides insights into things like: Committed vs.…

Hi @khushboo_puri ! It’s a little difficult to understand exactly what you mean — could you perhaps share a couple of screenshots so I can see the case more clearly? In theory, the behavior could be explained like this: The first transition to In Progress may have been on 27 Aug 2023 (about 2 years ago). But if the issue…

Hi @Afrooz Kasraei , Here’s the quick version that’s worked well for mixed FE/BE/mobile teams: Pick the method that matches your work: Story points → best when complexity varies. Keep it simple: Fibonacci, 3–5 reference stories, and quick calibration in refinement. Issue count → great if items are similarly sized. Pair…

Hi @Robin Jackson 👋 If you need automatic tracking, the reliable path in Jira Cloud is workflow + assignee–based timing, not “screen open/close” (Jira doesn’t emit a stable event for opening an issue tab). What teams typically track: Assignee Time – how long each agent owned the ticket (great proxy for agent work time)…

Hi @Florian Kreutzer ! 👋 Thanks for your question—just to clarify, could you share a bit more about what you mean by “automate the goals metric based on linked work item status”? Are you looking to: Automatically update a goal’s progress based on how many linked issues are in "Done"? Measure how long linked tasks stay in…

Hi @Jamie Stanczyk , Thanks for raising such a relevant question—reporting on individual capacity using story points can indeed be challenging in native Jira, especially across multiple projects or teams. If you're open to using a marketplace app, I’d recommend looking into the Sprint Report feature in the Time in Status…

Hi @christina.brooks , Welcome to the community! As an alternative, you might find the Sprint Report feature in the Time in Status app by SaaSJet helpful. This report is based on the JQL of your board, so it includes all relevant tasks across your selected projects. It provides detailed visual metrics such as: Sprint…

Hi @Dinakaran R , If you're looking to track issue age or custom SLA metrics in Jira, you can use the Custom Fields feature in the Time in Status app. It displays the time an issue has spent in its current status directly on the board and can be used in JQL. (Note: Only admins can create custom fields, and it's available…

Hi Usha 👋 That’s a good question — it’s common to see differences between issue history and the audit log. In short: Issue history tracks field-level changes. Audit log focuses on admin-level actions. If a change was made by automation, a bulk edit, or a system process, it might show in the issue history but not the audit…

Sorry for the delay @Rupendra Vengurlekar , These features aren’t supported natively in Jira Dashboards yet : Weekend exclusion Custom calendars You’ll need a third-party app for that — for example, Time in Status by SaaSJet (from my team, as I mentioned above) or other analytical tools available on the Marketplace.

Hi @Rupendra Vengurlekar , Yes, of course. It looks great. In my first comment, I just wrote down what I thought was best, but of course, we are working from the technical capabilities of the chart.

Hi @Gor Greyan , Our app, Time in Status by SaaSJet, currently cannot populate a custom field with logged time filtered by sprint. However, we do provide this data within the Sprint Report, where it’s calculated like this: Logged Time – The total time team members spent on each work item during the sprint, based on worklog…

Hi @Rupendra Vengurlekar , Great to hear you're exploring the new Dashboards beta in Jira Cloud! Let’s break this down based on the metrics you’re aiming to plot — Cycle Time, Lead Time, and Time in Status — and how that relates to choosing the correct x-axis value. Understanding the Metrics Lead Time typically measures…

Hi @Keira Wilkinson , 1. Verify the sprint's start date and time, ensuring it's accurate and reflects the actual start of the sprint. 2. When did you set the estimates? If you set them after the start of the sprint, the chart will not display any information. 3. If a sprint is started before issues are added or if issues…

Hi @Lareb Umer , That’s a great question, and a challenge we often see with teams managing multiple projects and sprints across different contributors. You might want to take a look at Time in Status app (developed by our team at SaaSJet). It’s specifically designed to give you deeper visibility into how work is…

Hi @Subbulakshmi K Great question—incident and unplanned work tracking often gets overlooked in sprint planning, but it’s crucial for teams with recurring operational load. One tool we’ve developed to help with this is Time in Status (built by my team at SaaSJet). While it doesn’t estimate effort directly, it does give you…

Hi @Lisa Fren , I completely relate to your situation - streamlining Sprint Reviews and clearly communicating with Product Owners and stakeholders can be challenging. Our team has previously faced similar challenges, which motivated us to create the Sprint Report as part of our Time in Status app. The Sprint Report was…

Hi @Rick Love , Above, you've already mentioned that you're trying to use the Average Time in Status gadget natively in Jira. When configuring the gadget, simply click once with the left mouse button to select the status you want to display. If you’d like to display multiple specific statuses, hold down the CTRL key (or…

Hi @y.masam , If you'd prefer not to count issues manually, you might find the Sprint Report in our Time in Status app helpful. It clearly shows counts for both completed and carried-over issues per sprint, allowing you to quickly review sprint outcomes. Feel free to explore the detailed documentation or let me know if you…

Hi @Satyajit Das , If you're looking for an easy way to compare Committed versus Completed issues, you might find the Sprint Report feature of our app, Time in Status, useful. It visually displays committed versus completed work, team velocity, scope changes, and other key metrics across sprints, enabling you to easily…

Hi @Prajwal Sapat , According to the documentation of the Velocity Chart: "The fact that the Velocity report doesn't take into account added and deleted tasks after the sprint starts doesn't give us a complete picture of the sprint. " Not taking into account subtasks does not give a complete picture. If you don't mind…

Hi @Vasanth Krishnan , The Cumulative Flow Diagram (CFD) in Jira is typically designed for individual boards or teams, providing a clear view of workflow progression within that team's scope. Unfortunately, native Jira features don't directly support creating a single CFD for multiple Scrum teams working on a unified…

Hi @Paul Singh , If you're open to using apps, I'd love to recommend something we've built — it's called the Time in Status app. One of the handy features is that it adds custom fields showing how long an issue has spent in each status, right on the issue card. You can also use this data in basic automation and JQL…

Hi @Akhand Pratap Singh I can advise you to try using the Time Metrics Tracker | Time Between Statuses app developed by my team. In it, you can measure the time between statuses and generate reports based on these metrics. Yes, the app won't be able to send reminders directly to users. However, you can set time limits for…

Hi @Dhruti Shah , You have already been advised how to do this with Jira Automation. If you don't mind apps from the Atlassian Marketplace, you might find the Time Metrics Tracker | Time Between Statuses app developed by my team useful. With it, you can measure the transition time between statuses you need and add the…

Hi @John Moore , 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 completed sprints, empowering teams to make…

Hi @Sushmita Chakraborty , If you want to track the time spent in a ticket based on ticket status changes, I recommend using reports in the Time in Status app (developed by my team). You will be able to track the time spent in each status, and, if necessary, create a status group called Resolution Time, etc. I hope you…