Alexey Pavlenko (App Developer) Atlassian Partner

With the new Q&A experience, I'm seeing answers marked as accepted even when they contain nothing more than a screenshot or a short comment that doesn't explain what actually solved the issue. It was like that before as well. There are enough cases where the wrong or meaningless answers are marked as accepted and the…

Hi @Takiar, Vishal (B2B - Infosys) Natively, unfortunately, it's rather not possible to track. The closest native gadget would probably be Cumulative Flow Diagram. You can try as an option the app I developed…

@Shailesh Yadav yes, it's a JIRA gadget which is integrated with JIRA dashboards. * Ask your JIRA adminstrator to install the app on your JIRA instance. * On the Dashboard, click "Add gadget", search for "Multi-team Metrics", click "Add". * Configure the gadget according to my recommendations above. In addition, you can…

Hi @Naveena Tati , Multi-team Scrum Metrics & Retrospectives covers all your requests. * Sprint starts with 50 issues/How much work was committed at the beginning of the sprint = Initial Scope * Only 2 new issues are created during the sprint/if additional scope was added during the sprint = Added Scope * 20 issues are…

Hi @Radhika Vijji, You can use Multi-team Scrum Metrics & Retrospectives for that. Quarterly commitment: Choose Period = Quarter, and you will get the view like this with the drill-downs into the lower periods (months and sprints): ... Story level reporting, sprint level reporting: Just change the Period to Sprints and you…

Hi @Deepali Dabholkar , Natively, unfortunately, it's not possible. You can accomplish it with Multi-team Scrum Metrics & Retrospectives. Below is the Chart configured for the Issue Count. 3 boards/teams in the same view, 1 period selected for analysis: 3 boards/teams in the same view, all periods are clicked for average…

Hi @Shailesh Yadav , Natively, unfortunately, it's not possible to do this. You can accomplish it with the app I developed - Multi-team Scrum Metrics & Retrospectives. Using the custom JQL metric feature, create whatever filters/metrics you want whether it is priority or status Using the Measurement Unit (Y-Axis), select…

Hi @Balakumar , What do you expect to see on the Y-Axis - 3 data points: * Small (1) * Medium (2) * Large (3) ? So the bars representing tasks will have only 3 discrete height levels? Best regards, Alexey

Hi @Fabricio Riveros , Unfortunately, natively in JIRA it's not possible. However, with the app I developed - Multi-team Scrum Metrics & Retrospectives, you can cover all these requests: 2. Identify issues that have been carried over across multiple sprints - Uncompleted Scope metric. 3. Calculate rollover/carryover…

Hi @Antoaneta Iskra , During sprint planning, I want to have visibility into each person’s workload in terms of available hours For detailed capacity planning, I would recommend the Jira Premium plan which comes with Jira Plans. Jira Plans has team and individual capacity planning. while still being able to monitor team…

Hi @Balakumar , Since you have a Premium plan instead of an Enterprise plan, this feature is not available to you unfortunately. As an alternative, you could try the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can: * Track:* Data across sprints, months, quarters, half-years or years. * Several…

Hi @Goran Stoyan , Personally, I've never seen a team utilizing the auto-scheduler in practice. Everyone I know from major and leading companies who has tried the auto-scheduler has ended up switching to manual scheduling whether for team usage or for stakeholder alignment. A good supplement to JIRA Plans can be an app I…

Hi @David Ludwig , How much do those 8 teams have in common? Is every component - a separate domain? If so, what you are doing makes sense, but keep in mind that in this case you normally have separate Scrum Events, along with a separate Scrum-of-Scrums meeting where one person from each team attends for a cross-team sync.…

Hi @Golden Glow Cleaners , After working with multiple teams for several years in JIRA, I came to the conclusion that there were too many limitations in tracking and improving performance of multiple teams. Due to that I've created an app - Multi-team Scrum Metrics & Retrospectives. With it, you can: * Track:* Data across…

Hi @Alexandre Paiva de Lacerda Costa , There is no documentation on Sprint Capacity Analysis, unfortunately, but if you have concrete questions - you can post them here and we will try to help you out. As an alternative, you can try the app I developed - Multi-team Scrum Metrics & Retrospectives - which contains a Capacity…

Hi @Lujain Aljaafari , 1. For one space with several teams, what's the recommended pattern in the new Jira experience — components + filtered boards, one project per team, or something else? created multiple boards in one space and scoped each with a board filter plus Components per team. If the Components field is not…

Hi @В_ячеслав Плахутін , Could you please take a look at the solution I implemented - AI Code Pulse: Total Cost and Efficiency of AI-coding? From what I can tell, this is exactly what you are looking for, plus the app can track: * PR Cycle Time for any period * Rework rate - code waste and survivability, missing…

Hi @Haya Bawati , Alternative approach might be using the app I developed - Multi-team Scrum Metrics & Retrospectives. 1. Create a custom JQL filters per feature. 2. Check the 3 boards/teams in the same view, 1 period selected for analysis (Instead of Total Defects, it might be $1M Opportunity): 3 boards/teams in the same…

Hi @Bailey Lissington , Yes, usually people create boards per smallest group of people. Especially when you need separate reports. But it comes with a trade-off, you will need to switch between team reporting tabs constantly in order to check each report. If you need a unified view, you can try the app I developed…

Hi @Kim_Vencill , Yes, the Control Chart is not configurable, unfortunately. With my app AI Code Pulse: Total Cost and Efficiency of AI-coding you can track PR Cycle Time for any period and get average, plus: * Rework rate - code waste and survivability, missing implementation parts - this is one of the few crucial signals…

Hi @Chris Berry, The Velocity Report is not available for non-finished sprint, unfortunately. If you need this functionality, you can try the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can: * Track:* Data across any sprints, months, quarters, half-years or years. * Several teams (including…

Hi @sonali , For solving this, you need to adjust your board JQL. Otherwise, if you would like to keep the board JQL the same, you can use the app I developed - Multi-team Scrum Metrics & Retrospectives. Use the Custom JQL filters to apply additional filters on top of any metric (to filter out the unwanted items). And you…

Hi @Gordon Varney, There is no out-of-the-box solution even on the marketplace, but most of it can be configured with Automation. For the rest, you can use the JIRA REST API. However, not for the sake of advertising, but for the real usage, I would recommend you just try my app - Multi-team Scrum Metrics & Retrospectives -…

Hi @Rebecca Hylek , I would try to exclude cancelled tasks from the board JQL itself. Therefore once the tasks are cancelled, they disappear. Another option in order not to change the board JQL and have more flexibility - the app I developed - Multi-team Scrum Metrics & Retrospectives - with it you can use custom JQLs on…

Hi @Laura Turbe , As an additional approach - consider the Quantifiable retrospectives (the most popular article for more than 4 months in a row). It can significantly improve your overall performance and retrospectives specifically. Best regards, Alexey

Hi @Syeda Raeesa Batool , The app I developed - Multi-team Scrum Metrics & Retrospectives - might be useful for you in the future for tracking and improving performance of multiple teams or just big programs/projects in general. With it, you can: * Track:* Data across sprints, months, quarters, half-years or years. *…

Hi @sergio cal , The app I developed - Multi-team Scrum Metrics & Retrospectives - doesn't cover what you outlined, but it might be useful for you in the future for tracking and improving performance of multiple teams. With it, you can: * Track:* Data across sprints, months, quarters, half-years or years. * Several teams…

Hi @Caryn Yeoh , If every project has a scrum board, you can solve the task using the app I developed - Multi-team Scrum Metrics & Retrospectives. 3 projects/boards/teams in the same view, 1 period selected for analysis: 3 projects/boards/teams in the same view, all periods are clicked for average metrics and dynamics:…

Hi @Tanvi Sharma , Reliably and without any 3rd party apps, you will need to use Jira's REST API and build your own solution. That's the only way, unfortunately. If you consider 3rd party apps, you can try the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you can not only track the work done vs the…

Hi @scott_norris , As a replacement, you can try the app I developed - Multi-team Scrum Metrics & Retrospectives. With it, you will get not only Sprint Goals and tasks assigned to a sprint, but also: * Completed Scope out of Final Scope (=manually calculating the progress %) * Data across sprints, months, quarters,…