Comments
-
Hi @shay ron Great to hear that you're exploring solutions to track status change timestamps! Regarding the empty fields you mentioned—Change Completion Date and Time to Resolution—these fields are typically part of Jira Service Management or custom SLA settings, and their functionality depends on specific configurations.…
-
Hi @andrejkovicovar 👋 Understanding the timeline of an issue in Jira can be tricky, especially when relying on the visual dots representing days in status. To double-check the exact date an issue transitioned into a specific status, the built-in Jira functionality might not always provide a clear answer. However, if you're…
-
@Anahit Sukiasyan I'm glad you found the article helpful! 😊🎉
-
Hi @Omri Zeman, Alternatively, if you’re regularly working with mentions and need a more streamlined way to manage them, have you checked out the Mentions Dashboard for Jira? It’s a gadget that helps you track and manage all mentions in Jira comments. This could complement your automation by giving you a centralized view…
-
Hi @Kashif Rahman It seems you want to create a filter to identify issues resolved within the last 30 days that took more than 7 days to resolve. While the JQL query you provided points in the right direction, it seems there's some misunderstanding regarding the use of timespent and how it calculates durations.…
-
Hi @Eftychis Fetfatsidis 👋 and everyone who is looking for a solution.Jira's native dashboards do not allow the exclusion of weekends from calculations, and these options lack the flexibility and advanced features necessary for fully customized and accurate time tracking.If you’re looking for an easy way to enhance…
-
Hi @Jeremiah 👋 and everyone who is looking for a solution.If you’re looking for an easy way to standardize and enhance reporting across all service projects, the Time Metrics Tracker add-on can be option for you. Time Metrics Tracker allows you to track key metrics between statuses like SLA, Time to Resolution and…
-
Hi @Peter Grainger 👋 and everybody who is looking for solution.Adjusting SLAs is a common scenario when fine-tuning team workflows. Here’s how Jira handles SLA changes and how you can further enhance your reporting:How SLA Adjustments Work: * When you increase the SLA time, newly created issues will automatically follow…
-
Hi @Fabrício Diego Ferreira and everyone who is looking for the solution. Here are some metrics that can provide valuable insights for your team, especially in a company-managed project: 1. Cycle Time * Why it's important: Tracks how long it takes to complete a task from start to finish. This metric helps you identify…
-
Hi @Chandra Mouli 👋 For you and everyone who is seeking for the solution, try out Time In Status add-on. It’s designed to help you visualize and analyze how time is spent in different statuses or transitions across your workflows. Here’s how Time in Status can help: * Custom Time Reports: * Track the time issues spend in…
-
Hi @Ken Wells Welcome to the community! It sounds like you're dealing with a unique use case where the "resolved date" doesn't align with the status changes you're looking to measure. Fortunately, the Time Metrics Tracker | Time Between Statuses. add-on can help you customize metrics based on the specific transitions…
-
Hi @Chandrashekar Nyathappa 👋 As mentioned by @Trudy P Claspill , you can't accomplish this using Jira's built-in solution. If you consider installing third-party add-ons to help, try out Time In Status add-on. You can easily get dashboard with status shown in the tabs like Review, Development, QA, Acceptance in column…
-
Hi @SianS It sounds like you're doing a great job tracking your team's development using the Sprint Reports. I suggest you to try Sprint Performance Report (which available throw Time in status add-on). The report automatically provides insights into key sprint metrics, including: * Committed work: The number of Jira…
-
Hi @[deleted] 👋 Creating custom reports in Jira depends on the type of information you're looking to track and visualize. For basic reporting, Jira's built-in tools, like JQL (Jira Query Language), and dashboards can help you get started. For example, you can use filters with JQL queries to define criteria such as: *…
-
Hi @Safa Al Shuaili 👋 Welcome to the Community! If you consider installing third-party add-ons, option for you can be Time In Status. Add-on has integration with eazybi, but its easier to extract duration of each status in your Jira. For this just: * Choose Project, Assignee, Sprint etc. * Filter issues by Time Ranges *…
-
@Learning123 Yes, you can see this for any past sprint. But just for the clarification, by “chart“ you mean gadget in dashboard or just visual representation?
-
Hi @Learning123 Also you can easily get BUG and STORY ratio per sprint in the same sprint board by Sprint Performance Report. Report is available throw the Time In Status add-on. Also add-on offers more built-in and custom reports for Scrum Teams which you can get by grid, charts or dashboards. You can also book a live…
-
Hi @Alicia Redden Welcome to the Community! You can easily get Assignee, Ticket Description, Status, Days in Progress (or something similar,) for all tickets assigned to several different Parent/Epics with Time in Status. You can also book a live demo - we'll show you the application inside out and answer all your…
-
Hi @Sorokach, Mark D Welcome to the Community! For metrics like Average % of Planned Velocity Accepted, Average User Story Cycle Time, Epic Lead Time you can try add-ons like Time in Status or Time Metrics Tracker With Time in Status you can easily get metrics like Cycle Time, Lead Time Report Or Average Time report Also…
-
Hi @Safa Al Shuaili 👋 Welcome to the Atlassian community! If an app from the Atlassian Marketplace is an option for you, look at the app that my team and I are working on, Time In Status. To extract duration of each status in eazybi Just simply: * Choose the Status Entrance Date Report * Filter issues by created, updated,…
-
Hi @Vera Valshonok 👋 Also solution can be Time in Status add-on. Which allows you to view the entire duration of an issue, from the time it was opened until it was closed, with the Time in Status report. You can also view the Open Ticket Date/Time and Closure Date/Time with the Status Entrance Date report, which displays…
-
Hi @Colleen Stone 👋 With my SaaSJet team, we built Sprint Performance Report where we have metrics such as Velocity, how much was committed, completed, etc. Report is available throw the Time In Status add-on. Also add-on offers more built-in and custom reports for Scrum Teams which you can get by grid, charts or…
-
Hi @Gregory 👋 Your project for a centralized performance dashboard sounds fantastic! Extracting detailed sprint data is indeed essential for tracking team productivity across multiple projects. While working with the Jira API can sometimes be challenging, I wanted to share an alternative solution that might save you time…
-
(deleted)
-
Hi @Celina Kim 👋 You might have to create your own solution or use a third-party app to access this data. So if you consider installing third-party add-ons to help, you can try Time in Status. The algorithm for excluding weekends is quite simple. First, you must set up your work calendar - add days off, breaks, holidays,…
-
Hi and great question @Petru Simion _Simitech Ltd__ 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 2 add-ons. Both Time in Status and Time…
-
@roumaissa hamidi Thank you!
-
Hi @Bill Sheboy Thank you for your recommendation! Edward Tufte's work is a fantastic resource for understanding effective data visualization, and I'll be sure to revisit The Visual Display of Quantitative Information for deeper insights!
-
Hi @Vera Valshonok If you need more precise report, you can try out Time Between Statuses add-on. This tool is great for precise reporting because it includes options like calendar settings (working days/hours) and allows you to customize transition settings (e.g., first time, last time, or total time in status). In your…
-
Hi @Jayanth I noticed that you are currently using the free Jira plan and have chosen not to use any add-ons. If your decision is primarily based on cost, I wanted to inform you that our add-on, Time in Status, will be available to your team at no charge. With Time in Status, the time will be accurately calculated, even if…