Data Source Type

Flow Analytics integrates with your Jira setup, offering several Data Source types to tailor your charts to your team's workflow:

• Jira Board: Visualize visualize progress using Scrum and/or Kanban boards.

• .

• JQL: Utilize utilize saved or custom JQL queries for accurate filtering, which is ideal for complex or customized data selection.

• Initiatives: Track track the progress of specific strategic issues, getting new insights and a fresh view of how it is going.

Expand
title What does the Initiative means
In a Scaled Agile environment, the Jira process needs structuring with complex hierarchies beyond standard offerings. Enterprises adapt by renaming and creating new issue and link types, building an issue architecture above the basic Epic-Story-Sub-task structure. Adjustments typically involve creating 'boxes' for the Program level and 'boxes of boxes' for the Portfolio level. Medium-sized businesses may use just one level above the Epic. Commonly, Program Epics are on Level 1, and Initiatives on Level 2 of this hierarchy: Image Added In chart settings, to create a chart for a particular scope, you can select the top-level issue for tracking, set the hierarchy depth, and specify the link type to exclude irrelevant links (e.g., “blocked by”): Image AddedImage Added To understand how it works, let’s look at the following cases based on the example hierarchy mentioned above: If you have selected Initiative, depth 2, child of / parent of, then the chart will show you the data from all Stories and Tasks from all Epics linked to all Program Epics linked to Initiative. If you have selected Program Epic, depth 1, child of / parent of, then the chart will show you the data from all Stories and Tasks from all Epics linked to all Program Epic. If you have selected Initiative, depth 1, child of / parent of, then the chart will show you nothing because there are no Epics linked to Initiative directly. If you have selected Program Epic, depth 2, child of / parent of, then the chart will show you nothing because there are no Epics linked to Stories or Tasks linked to Program Epic.

• Epics: track higher-level progress by selecting “Epics by list” or “JQL” query.

Data Source Unit

Boards

• Select multiple Scrum and/or Kanban boards for a unified view.

• Combine Scrum and Kanban boards on a single chart for a comprehensive view.

• Add or remove boards as needed.

• If you don’t see the needed board in the list, start typing the name, and the search will find it.

JQL

• “Saved JQL filter” ensures consistency and saves time when applying commonly used filters.

• “Custom JQL filter” offers maximum flexibility, allowing you to target specific issues or custom fields that align with your project's requirements.

Expand
title Examples of how the JQL can be used
Filter issues from Scrum and Kanban boards at the same time Given: You have two teams working in two different methodologies: Scrum and Kanban You want to track their progress as one team of teams In that case, you can create your own Custom JQL filter: Filter issues from a particular Release/Epic across all boards Given: You have more than one team working on some Release (or Epic) You want to track their progress as one team of teams In that case, you can create your own Custom JQL filter:

Initiatives

In a Scaled Agile environment, the Jira process needs structuring with complex hierarchies beyond standard offerings. Enterprises adapt by renaming and creating new issue and link types, building an issue architecture above the basic Epic-Story-Sub-task structure.

Adjustments typically involve creating 'boxes' for the Program level and 'boxes of boxes' for the Portfolio level. Medium-sized businesses may use just one level above the Epic.

Commonly, Program Epics are on Level 1, and Initiatives on Level 2 of this hierarchy:

Image Removed

In chart settings, to create a chart for a particular scope, you can select the top-level issue for tracking, set the hierarchy depth, and specify the link type to exclude irrelevant links (e.g., “blocked by”):

Image Removed

Image Removed

To understand how it works, let’s look at the following cases based on the example hierarchy mentioned above:

• Track the issues related to the Initiatives by “Linked issues” or the “Parent field” method.

• Choose between 1 or 2 levels to display parent-child relationships within your initiatives.

• Specify the type of linking for issues, ensuring accurate tracking of dependencies and relationships.

Epics

• Select the Epics through a list to see the aggregated data for the related to each other themes.

• Use the JQL to focus on key project elements and expand or narrow the wished Epic's scope.