Vasyl Krokha _Broken Build_ Atlassian Partner

Hi @Marino Poletine , When each scrum team has its own board and project, getting a unified view of Epic progression across all of them can be challenging - Jira doesn't offer a native way to consolidate this. With Agile Reports and Gadgets, you can build an Epic progress report or an Epic burnup chart on your Jira…

Hi Jim! The problem: You want to automatically display burndown charts and sprint reports on a Confluence page to keep stakeholders informed - without manual effort each time. Manually recreating charts on Confluence each sprint is tedious and error-prone - stakeholders need live data, not stale screenshots. The solution:…

Hey John! The challenge: You want a proper Cumulative Flow Diagram to visualize how work flows through your process - tracking arrivals, departures, and WIP - but building one manually in Atlassian Analytics requires significant effort to replicate the stacked-area logic, status groupings, and trend lines that make a CFD…

Hi @Jamie Scott , The core issue is that JQL-based approaches like closedSprints() with resolved dates don't accurately attribute story points per sprint - they can miscount items that moved between sprints or changed estimates mid-sprint, which explains why your previous sprint totals look wrong. A proper…

Hi Wendy! Jira's built-in burndown/burnup reports are tied to sprints and don't work well when you need to track progress at the Epic level - especially with custom issue types. Exporting to Excel is one workaround, but it's manual and hard to maintain. There's a Jira app called Agile Burnup Burndown Charts that addresses…

Hi Jim! The challenge: Jira's built-in reports are team-oriented and don't offer a straightforward way to visualize an individual user's delivery - such as completed vs. estimated work, story point trends, or progress over time. A solution: The Individual Velocity Chart in Agile Velocity Charts is specifically built for…

Hey Lira! You're running into a very common limitation - Jira's built-in reports are designed for single-board, sprint-level views and don't offer monthly grouping, target lines, multi-project aggregation, or the kind of executive-ready visuals that leadership typically needs. The good news is that Agile Reports and…

Hello, Bud. In Jira's native Burnup Chart, the remaining work is not explicitly shown on the chart. I've checked the Sprint Report and Burnup Chart for different sprints on my production environment - here are a few hints that may help you: 1. Burnup Chart - on this chart, the remaining work is the gap as shown below: 2.…

Hey Colleen, the native velocity chart only allows you to see velocity data for 1 team and can't be added to the Jira dashboard. These limitations were among many reasons why we created the Agile Velocity Chart Gadget. So, if you're open to using third-party apps, I would recommend giving it a try. With the Velocity Chart…

Hi Sangeetha, Native Jira tools don't provide a gadget for velocity tracking, so you're probably using a third-party app. In case you're using the Agile Velocity Chart Gadget, you can easily add multiple teams and analyze unlimited sprints if you open the Settings here: And configure the chart as follows: If you're using…

@Whitney Nicholes hi, the voting is now open, yet our best video is not listed.. could you please fix this so we won't miss any votes? https://community.atlassian.com/t5/App-Central-articles/Who-s-your-Agile-dealer-Agile-Reports-and-Gadgets-blues-for/ba-p/2841589 

@Stephen_Lugton @Michael Kerr @Lucas_DevSamurai_ @Kishan Sharma if you enjoyed the first Sarah's adventure, there are two more videos that we posted for the Apptoberfest'24 (both of them featuring Sarah): Who's your Agile dealer? 😎 Agile Reports and Gadgets blues for 🎷 Apptoberfest'24 🍻 👀🍺 Spotting bottlenecks and necks of…

@Janice I overlooked this, sorry - will remove the link now.

Hi, @Priyanka Jadeja ! Could you tell me for what purpose you need this list of issues? If you need to share the list as a screenshot or review them with your team, you can use one of those apps: * Agile Reports and Gadgets - for scaled enterprises (Scrum, Kanban, SAFe, Less, SoS). * Agile Velocity Chart - for smaller…

Hi, @Yi Meng Jira has a lot of limitations when it comes to tracking in multi-team environments, especially when your teams have slightly different setups. That's why we created two reporting apps: * Agile Reports and Gadgets - for scaled enterprises (Scrum, Kanban, SAFe, Less, SoS). * Agile Velocity Chart - for smaller…

Hi, @Dheera Chaturvedi Based on my experience, the executives want to examine the big picture of the project's progress, focusing on critical Epics and Features. To provide Epic progress, you have to assess the progress of the issues inside. The best way is to count completed story points every sprint (or week, if that's…

Hi, @Carrie Pickering It seems to be a bug in Jira. You can run a zero-cost test and find out whether there is a problem with the Jira Release Burndown report or with some hidden story points in your release issue list. To run this test, please follow the next steps: 1. Install the Agile Reports and Gadgets app from the…

Hi, @Floreana Di Trapani Jira Cloud comes with limited reporting options, and you can't even select which sprints to show. That's why we created two apps: * Agile Reports and Gadgets - for scaled enterprises (Scrum, Kanban, SAFe, Less, SoS). * Agile Velocity Chart - for smaller companies with only Scrum teams. Both of the…

Hi, @Bireshwar Das It seems that the Reporting feature isn't enabled. If you are the project admin, you can switch it on: FYI: There is blasting Velocity Chart Gadget app on Atlassian marketplace, which has much more to tell you about the sprint health. You can try it for free and find in you project left bar menu:

Hi, @Pooja Wandile That's the problem with the JQL search and working via API; both approaches offer only the final state of a particular issue. That's why the majority of reporting apps can't be utilized in dynamic environments where estimation and other fields change frequently. That's why we created two apps: * Agile…

Hi, @Casey Enderlein Unfortunately, Jira doesn't provide such a feature from the box. That's why we created two apps: * Agile Reports and Gadgets - for scaled enterprises (Scrum, Kanban, SAFe, Less, SoS). * Agile Velocity Chart - for smaller companies with only Scrum teams. Both apps include the capability to see delivery…

@Asokan Manickavasagam gotcha. Just in case you are not planning to use 3d-party apps due to security and compliance reasons, we are Cloud Fortified, meaning we meet Atlassian requirements for safety and data protection. That's why our apps are used by: Whenever your factors change, please do not hesitate to book a demo…

Hi, @Asokan Manickavasagam Jira doesn't provide such capability, but there is Agile Reports and Gadgets app, which has cross-team Velocity chart allowing you to see several teams on one chart: And also you can export the chart data to .csv: Or even generate a Live Data link to pull date to your sheets automatically: Hope…

@Mike Oragwa What do you mean? Do you have it installed in your Jira? I've changed the link (there was a data center option selected by default, and I changed it to a general link). Could you try one more time?

Hi, @Mike Oragwa As mentioned above, the sprint has its specifics, and it’s important to have an estimated scope before the sprint start date and complete it before the sprint completion date. To investigate what’s happened, you can try (for free) the Velocity Chart Gadget app because it shows much more than Jira: If the…

Hi, @Andy Rosengard ! We have a board that aggregates from several projects and Jira shows insights: So, it could be some internal problem with Atlassian, so it would help to create a ticket in Atlassian support. By the way, the Agile Reports and Gadgets app (which you can try for free) works with all types of setups - you…

Hi @Roy I don't think the fields in the child issue list are configurable since you could not find how to do that in the documentation. What you could using Scrum Velocity Chart gadget of the Agile Reports and Gadgets app is to see epic child issues split by sprint and many more. All you need to do is to specify your Scrum…

Hi @Sven Horner Can you share a sprint details screenshot with issues? All the details can be hidden except statuses and estimations. Also, can you share your Scrum board columns to statuses mapping the board configuration? All built-in Jira reports are calculated on the fly, so all configuration changes are considered…

Hi @Shiva Kumar Burgu You cannot configure the built-in Velocity Chart report, but you do it in the Velocity reports of Agile Reports and Gadgets app: * sprints * sprint metrics So that the Velocity Chart looks like below. You can read more about Velocity report in the documentation. We are happy to help via…

Hi, @Lilit Tsaturyan! With Agile Reports and Gadgets app, you can select what type of tasks you want to count, when using Time Tracking fields: The Velocity chart can say you about given sprint more then only scope change and completed metrics: You can try it for free here. Hope, you find it helpful. Vasyl