Numerous Several applications within Jira are specifically designed to manage handle Scaled Agile Organizational Structures in Jira go beyond the fundamental , going beyond basic Projects and Boards. These tools incorporate cover Programs, Agile Release Trains (ARTs), Portfolios, Products, and Product Lines to enable comprehensive make reporting a breeze. They also utilize make use of custom JQL (Jira Query Language) filters for defining precise to pinpoint data scopes in Velocity and Burnup Charts.

A challenge emerges when integrating Now, here's the tricky part. Integrating these abstract entities with board context to obtain pull out Sprint or Kanban metrics for larger organisational organizational units , such as like Divisions or Product Lines, which often consist of dozens of teams, each with its have multiple teams with their own team-level boards. The process of selecting numerous boards as data sources every time new charts are created becomes cumbersome.To tackle this issue, we introduced , can get a bit overwhelming. Imagine having to pick multiple boards every time you want to whip up some new charts - talk about a hassle!

But fear not, we've got you covered with the 'Board set' feature. This feature simplifies the aggregation of nifty tool makes it super easy to gather Sprint and Kanban metrics for large units by enabling the selection of bigger units. With just one click, you can select multiple boards as a single data source with just one click, thereby streamlining , making the chart creation process a walk in the park.

Create board set

To start utilising board sets instead of individually adding boards each time you create a chart, there are two approaches:

...

You can edit the board set at any time: Image Removed

...

The board set will be automatically updated across all charts, meaning charts with edited board sets will display the updated data.

...