Seitenvergleich

The Agile Planning Popup is integrated on the JIRA Agile Board and can be accessed where you need it during sprint planning, dailies or sprint review meetings. 

1: Open the popup in menu 'Agile Planning' and 'show aggregation'.

2: You can select different view modes:

• Parent Issues only: Estimations of Backlog entries will be summed up (like in JIRA standard).
• Sub Tasks first: Estimations of sub tasks will be summed up, if they exist. Otherwise the estimation of the parent issues will be added. (Default)
• Sub Tasks only: Estimations of sub tasks will be summed up, if they exist. Estimations on parent issue level will be ignored at all with this method.
• Both: Estimations of the parent issue AND the subtasks are summed up.

Check out example below!

3: Aggregation mode is by task now. You can toggle between by issue, by assignee, by status and by column. It's also possible to select a custom field to aggregate on, that you have to configure on the Agile Planning administration page.

4: Select the sprint, you would like to see. Default is the currently active sprint. On Kanban boards sprint selection is disabled.

• Parent Issues only: Result is 1 week as just estimation of parent issue (Backlog entry) is estimated.
• Sub Tasks first: Result is 1 week 3 days as subtasks exists for this parent issue, so subtasks will be summed up and parent estimation is ignored.
• Sub Tasks only: Result is 1 week 3 days as only subtasks are summed up.
• Both: Result is 2 week 3 days as estimations of the parent issue AND the subtasks are summed up.

Let's have a closer look at the columns for the issue based list.

• Icon: Represents the type of the issue. If the ticket contains sub-tasks the icon for sub-tasks is shown for each view mode to highlight that they exist.
• Name: A link represents the parent issue. The summary of the issue is shown below. Full text is visible by mouse-over.
• Issues: Counts the relevant tickets that are summed up accorfing to the selected view mode. 

• 
  1 parent and 2 sub-tasks for 'sub-task first' view mode count is 2. For view mode 'parent issues only' count is 1.
• Orig. estimate: Shows the original estimate summed up according to the selected view mode.
• Rem. estimate: Shows the remaining estimate summed up according to the selected view mode.
• Logged work: Sums up the logged work time of the issues according to the selected view mode.
• Difference: Shows deviations - difference = orig. estimate - rem. estimate - logged work
  Check out example below!

Detect deviations from original estimates easily!

If a sprint is started and the team would raise remaining estimates this is highlighted in column difference. The team can check and discuss these cases in dailies for example.

Define custom fields for aggregation modes

If you have defined custom fields in Jira, it is possible to use them for aggregation. To use a custom field for aggregation, you have to add it in the Agile Planning Administration.

1. Open the Agile Planning Administration page (Jira Administration -> Add-ons -> Agile Planning Administration)
2. Select the custom field you want to add from the select field
3. Click on the 'Add' Button next to the select field

To remove a custom field from the list of available aggregation modes, click on the 'Remove' button next to the custom field you want to remove.