Release Notes for 10.78

• Enhancements and Features
• Defect Fixes

Enhancements and Features 

Aligned story counts

To correct defects reported for mismatching story and story point counts across the Stories grid, Work Tree (Bottoms-Up view), Program Room, and Program Increment Progress pages, we've changed the way stories are counted according to their sprint and program increment assignments. Sprint assignment will be primarily used to determine if stories are included in displays and counts.

When filtering a page by program increment, a story will display and/or be included in count values if:

• The story's Sprint field is set to a sprint associated with the selected program increment
• The story's Sprint field is set to Unassigned Backlog and the Program Increment field is set to the selected program increment

Misaligned stories, which have sprint and program increment assignments that do not match, will display based on the Sprint field and its association with a program increment. See Manage Stories with the Story Grid for examples.

This change addresses JIRAALIGN-1553. See the Calculations section of the Defect Fixes table in this article for more details.

Team Load vs Capacity enhancements

To help you understand a team's workload and capacity when planning for and executing a program increment, we've updated the Team Load widget inside of the Program Room. The widget has been renamed Team Load vs Capacity to better reflect its purpose: 

For each team in the program increment, a row displays with a percentage value of load vs capacity. The value is calculated as follows: (Program Increment Load / Program Increment Capacity) * 100. 

• Program Increment Load - The sum of story points assigned to the team, associated with the program increment (see the Aligned story counts enhancement above)
• Program Increment Capacity - The sum of team velocities for each sprint in the program increment
  • A team's velocity will use one of three values for each sprint: Average Team Velocity, Accepted Points, or Override Velocity
    • Average Team Velocity - The average of all accepted story points from the last five completed sprints. This value is used to calculate Program Increment Capacity when a sprint has not started, and no override velocity is present.
    • Accepted Points - The number of story points in the sprint. This value is used to calculate Program Increment Capacity when a sprint in the program increment has been completed.
    • Override Velocity - Override value entered for a sprint, useful for anticipating sprints that will have reduced team capacity, increased headcount, or are new to the program. This value is used to calculate Program Increment Capacity when a sprint has not started and an override is present.

Click a row inside the Team Load vs Capacity widget to launch the team's Details panel, focused on the Sprints tab. There you can use the Team Details panel enhancements to review Average Team Velocity and velocity values for each sprint.

The % of load vs capacity in the widget will change as the PI progresses, as the team's Program Increment Capacity and Average Team Velocity values will update after the completion of each sprint. 

This change addresses JIRAALIGN-1914 and JIRAALIGN-1241. See the Calculations section of the Defect Fixes table in this article for more details.

Team Details panel enhancements

We've updated the Sprints tab inside of a team's Details panel to show more information about velocity. 

Additions:

• Average Team Velocity value added to the top of the panel
• Completed sprints used to calculate Average Team Velocity are highlighted in the table of sprints
• Three columns have been added to the table of sprints:
  • P - Planned story points
  • A - Accepted story points
  • OV - Override velocity (if applicable)

New REST APIs available

The following objects and methods are now supported in the API 2.0:

• Acceptance criteria can be updated on features using the PUT or PATCH methods
• Value streams and process steps can be read using the GET method

Performance: Users dropdown replacements

For better performance when selecting entries in user-based dropdown menus, we updated the following fields inside of work item Details panels:

• Dependencies - The Owner field inside of the Manage External Entities menu has been changed to a searchable, autocomplete field
• Features, Capabilities, and Epics -  The Analysts/Approvers and Customers fields inside of the Build Value Hypothesis menu have been changed to the new user dropdown design that loads results by portions and supports search

Defect Fixes