The Group By functionality on the Program Board enables users to organize work items into customized, concise views based on different criteria. This functionality offers multiple grouping options, providing tailored perspectives on work items, statuses, card types, and more. Below are the available Group By options accessible at the top of your Program Board.
In this article, 'Feature' is used as a general term and may correspond to the 'Epic' issue type in Jira.
Grouping Options
Features
Card Type
Status Category
Jira Project
Responsible (Features)
Responsible (Stories)
Jira Fields
Assignee (Features)
Assignee (Stories)
Selected Custom Fields (Enabled on the Edit Board Settings -> Additional Settings)
1. Example: Group by "Parent" (Parent of Feature)
This new grouping functionality on the Program Board organizes planned features by various criteria to enhance clarity and focus. Let’s begin with by selecting “Parent” grouping: when selected, the Board will arrange features as follows:
Groups of "Parent" bars are displayed in each team
The Parent setting must be done in the "Additional Settings" section.
Count at the group level represents the total number of features in that group
Each bar also displays Sprint labels, Estimate (Sum of Story Points), Status-wise item count showing the number of items in each status, and Dependency count.
2. Grouping Criteria Options
The other group by options displays the respective information in a similar pattern. Below table illustrates the outcome details of all the Group By options at the Program Board:
Group By | Details |
Feature | Features planned by each team are displayed in the same order as they appear on the Backlog.
If a feature is being worked on by multiple teams, it will appear under each team, but only the stories specific to each team will be shown in their respective sprint areas. |
Card Type | Kendis Card types |
Status Category | Sections for status categories (To Do, In-Progress, Done) |
Jira Project | Jira Projects for Features |
Assignee (Feature) | Sections for the assignee of the Feature as set in Jira. Regardless of whether the assignee is in Kendis or not, the value is retrieved from the Feature details in Jira. |
Assignee (Stories) | Sections by assignee, with all stories assigned to each team member. Similar to above section, the value is retrieved from Jira |
Jira Project | Groups by Jira Projects for Features |
2.2 Jira Fields
Default fields from Jira are listed in the table above. If more fields are selected from Jira, they will appear here. To set more fields
Go to Board Settings -> Edit Board Settings
Additional Settings -> Additional Fields
3. Team Area View
Grouping options are accessible within the Team view, allowing organizations to see features and stories organized by the selected criteria.
During Quarterly Planning sessions, a helpful grouping option is to view stories by the assignee.
In the Team Area, additional insights are uniquely available here:
Team Capacity: Defined manually or within the Team Capacity planning section.
Load: Total Story Points of all stories within each Sprint.
Committed Load: A baseline of the total Story Points set at the start of the Sprint.
The Grouping options are available under Team view. This enables organizations to view the features and stories planned by the selected criteria.
A valuable group by option during the Quarterly Planning session would be to view the stories by assignee.
In the Team Area, there is additional information that is only visible here.
Team Capacity: Set manually or set at Team Capacity planning area
Load: Sum of Story Points of stories in each Sprint
Committed Load: A baseline taken at the start of the Sprint for total sum of Story Points
