Comments
-
Hi @Anna Jelier , I am not the developer of the app you are using, but if the issue remains unresolved, I invite you to get acquainted with the Quantifiable Retrospectives. It might drastically shift your development. Best regards, Alexey
-
Hi @Corinne Guibert , Natively, it's not available, unfortunately. You can find it supported in the Roadmaps gadget which is part of the gadget bundle I developed - Heat Map, Projects, Roadmap, Labels Gadgets for Jira. Best regards, Alexey
-
Hi @joshalexandre , 7d is a hard-coded time frame, unfortunately, in JIRA. With my app AI Code Pulse: Analytics for Claude Code, Bitbucket, GitHub you can track PR Cycle Time for any period, plus: * Rework rate - code waste and survivability, missing implementation parts - this is one of the few crucial signals for…
-
Hi @Whitney Stambler , 1. Alignment is not possible, unfortunately. 2. Use a filter like this status WAS IN ("In Progress") BEFORE "2026/03/01" AND status WAS NOT IN (Done) BEFORE "2026/04/01" Save it and add after that to the "Filter Results" gadget. In the gadget configuration, add 'Time Spent' and 'Assignee' columns.…
-
Hi @mr john , I recommend introducing "Blocking" status additionally to issue linking. Best regards, Alexey
-
Hi @Chi-Yen Ho , There is no out-of-the-box solution for that, but there is an option that can be used as a workaround - Sprint Health Gadget - if you are ok with offsetting a little cognitive load - you will need to sum up several status categories - To Do, In Progress, Done, which is not a big deal. I would recommend…
-
Hi @Bala Sai Krishna , If you are on a DC instance, please skip my answer. If not, you can achieve what you want using my app Multi-team Scrum Metrics & Retrospectives. It won't be stacked bars but rather individual bars. You can do it via the custom JQL feature in the app. The result will look like this (for severity, the…
-
Hi @jason.roberts , I've been exactly in the same boat. I used my app for that - Multi-team Scrum Metrics & Retrospectives. You can select any period (active sprints supported), any metric (constructed via JQL) and any column to present. Best regards, Alexey
-
Hi @Hassen Alwalie , Speaking specifically about delivery risks, you can address them using the app I developed - Multi-team Scrum Metrics & Retrospectives. You can define any metrics you want to track using custom JQL feature inside the app. As a basic example, you can track unestimated or uncompleted tasks within a…
-
Hi @mr john , For keeping everything in sync, I constantly used my app with teams - Multi-team Scrum Metrics & Retrospectives. It also helped to improve the team performance drastically even without retrospectives. But when we used built-in quantifiable retrospectives, it improved the performance even further. 3…
-
Hi @Jose Delgado You can use the app I developed - Multi-team Scrum Metrics & Retrospectives for that. To get the screens below, the configuration that was used: * Period = Years (you can pick between sprints, months, quarters, half-years, or years) * Using the custom JQL metrics feature, "CustomMetric: Linus Comp Scope"…
-
Hi @Amit Singh , Do you use sprints? If so, you can try the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can view: * Data across sprints, months, quarters, half-years or years. * Several teams (including those ones sharing the same project) at once. * Velocity, capacity, allocation, completed…
-
Hi @Agarwal, Akshit , You have multi-week sprints and you want to track sprints on a weekly basis? If so, I think you need to derive the tasks you need using certain criteria in a JQL filter. Such as Sprint = "%YOUR_SPRINT%" AND resolutionDate >= %END_DATE_OF_YOUR_WEEK% resolutionDate <= %START_DATE_OF_YOUR_WEEK% After…
-
Hi @Rishab Taneja , I don't know if you consider custom apps, but with my app Multi-team Scrum Metrics & Retrospectives you won't need to conduct the migration between the two types of projects. Here is the view you can get with it: 3 boards/teams in the same view, 1 period selected for analysis: 3 boards/teams in the same…
-
Hi @Michael Green , Natively, it's not possible, unfortunately. The only way I see you can work around it is to name the latest sprint in the same manner all the time, therefore you won't need to update you hardcoded JQL filter. Alternatively - you can install my app - Multi-team Scrum Metrics & Retrospectives. You can…
-
Hi @Jim Tailor , For the Sprint Burndown Gadget, just type on the confluence page: /Sprint Burndown Gadget For the Sprint Report, I would suggest using the app I developed - Multi-team Scrum Metrics & Retrospective. First add it to a JIRA dashboard and after that add the link to the dashboard to the confluence page, it…
-
Hi @Marino Poletine , Please check native Project gadget. If you need something more sophisticated - you can try the Projects from the app I developed - Heat Map, Projects, Roadmap, Labels Gadgets for Jira. Best regards, Alexey
-
Hi @Patricia Modispacher _k15t_ , Thanks for the comparison article. Could you please add my app Multi-team Scrum Metrics & Retrospectives to your list as well? The app has supported reopens vs. done metric as well as percentage (%) rates from day one. Here are the screenshots: Setup: Reopened bar of 1 sprint is selected…
-
Hi @Penny Reid , If at some point, you will need a Velocity Report that supports SAFe - please keep in mind that you can refer to this one developed by me - Multi-team Scrum Metrics & Retrospectives. It supports aggregation/grouping sprints into months (Program Increment), quarters (Program Increment), half-years (Solution…
-
Hi @Roger Bradley , Maybe I am missing something, but, after reading your post, to me the total number of tickets in that timeframe = the number of times the field was left empty. If it's not the case, please distinguish the latter from the first one more clearly. Best regards, Alexey
-
Hi @Alex Lutterbach Sure, please share, it would be great to hear your experience. Probably, it would allow me to know how to approach something from a different angle than I am used to. Personally, I invested a lot of time into teaching stakeholders how to use JIRA, read dashboards and understand engineering. After this…
-
Hi @Jim Tailor , I must say that measuring individual performance contradicts agile principles, but if you are not trying to strictly stick to them, you can easily track, measure and even retrospect any individual metrics across sprints, months, quarters, half-years or years with the app I developed - Multi-team Scrum…
-
Hi @r_deepa , If you use Scrum, you can filter any statuses or metrics by a customer using the custom JQL metrics feature in my app - Multi-team Scrum Metrics & Retrospectives. In the example below, Completed Scope (or Done status) is filtered in additionally by assignee Rob. Instead of assignee you can filter it in by a…
-
Hi @Lira Martynenko , Natively, unfortunately, JIRA doesn't allow reporting by month. You can use the app I developed for that - Multi-team Scrum Metrics & Retrospectives. 1. how much our teams deliver = Completed Scope vs. what's planned = Initial Scope or Final Scope You can choose Initial Scope or Final Scope as a…
-
Hi @Sevastian , If you use sprints, you can use the app I developed - Multi-team Scrum Metrics & Retrospectives. * Select period: sprints, months, quarters, half-years or years. * Select teams. * Check "Initial Scope" vs "Added Scope" on the Charts. 3 boards/teams in the same view, period = Sprints, 1 period selected for…
-
Hi @Brian Black , Are you using the native Velocity Report? If so, as far as I know, it doesn't allow customization of columns nor assignee column. Best regards, Alexey
-
Hi @Kalpana BOS , Natively, unfortunately, it's not possible to choose Remaining Estimate or Time Spent for sprints. You can use the app I developed for that - Multi-team Scrum Metrics & Retrospectives. With it, you can get this view (look at the Y-Axis - Remaining Estimate (or choose Time Spent)): Best regards, Alexey
-
Hi @Aanchal Bhatnagar , Natively, it's not supported, unfortunately. You can try the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can view: * Data across sprints, months, quarters, half-years or years. * Several teams (including those ones sharing the same project) at once. * Velocity,…
-
Hi @Jamie Scott , project = X AND sprint IN closedSprints() AND status IN ("Completed", "Done", "Deployed to production") AND issuetype IN ("Story", "Bug") AND resolved >= "2026-01-01" I think in this query your are missing "AND resolved<=" for a starting point. You need time boundaries. If you need more than this in the…
-
Hi @Jack White , Natively, unfortunately, it's not possible to choose Remaining Estimate for sprints. You can use the app I developed for that - Multi-team Scrum Metrics & Retrospectives. With it, you can get this view (look at the Y-Axis - Remaining Estimate): Best regards, Alexey