Release Notes for 10.78


The old navigation will be removed from Jira Align in early 2024.
Learn more about the upcoming changes

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. 


Before the PI

Team A is preparing for the start of a new program increment and has been together for at least five sprints, generating an Average Team Velocity of 9 story points. Product management and the team have identified stories they will likely deliver in the program increment, spread across six sprints. This results in a Program Increment Load of 50 points.

Team A is anticipating bringing in an architecture expert to assist with the development of a story scheduled for Sprint 4. Knowing they will be able to deliver slightly more points with the additional team member, they set an Override Velocity of 12 points in Sprint 4. 

To calculate the team's Program Increment Capacity before the first sprint in the program increment begins:

Sprint Name Team Velocity Value Type
Sprint 1 9 Average Velocity
Sprint 2 9 Average Velocity
Sprint 3  9 Average Velocity
Sprint 4  12  Override Velocity
Sprint 5 9 Average Velocity
Sprint 6 9 Average Velocity


(9 + 9 + 9 + 12 + 9 + 9) =  Program Increment Capacity of 57 points

Team Load vs Capacity widget: (50 / 57) * 100 = 88%.

The team is optimally loaded with work for the PI, with some room to account for increased scope or unexpected blockers.

During the PI

Team A had a highly productive sprint and achieved a breakthrough that sped up the development. They were able to finish early and pulled in additional work. 15 story points were accepted in Sprint 1. 

The 15 points from the latest sprint increased the Team Average Velocity to 10.2 points.

While the team worked ahead, no additional stories were assigned to them in the program increment. This results in the same Program Increment Load of 50 points.

To calculate the team's updated Program Increment Capacity:

Sprint Name Team Velocity Value Type
Sprint 1 15 Accepted Points
Sprint 2 10.2 Average Velocity
Sprint 3  10.2 Average Velocity
Sprint 4  12  Override Velocity
Sprint 5 10.2 Average Velocity
Sprint 6 10.2 Average Velocity


(15 + 10.2 + 10.2 + 12 + 10.2 + 10.2) = Program Increment Capacity of 67.8 points

Team Load vs Capacity widget: (50 / 67.8) * 100 = 74%.

The team has more availability and may be able to help other teams or address additional scope. The team should review the increased average velocity and determine if it is sustainable, and then decide whether or not to increase Program Increment Load. 

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. 



  • 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:
    • - Planned story points
    • - 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

JIRAALIGN-1553 The Program Increment Progress report’s story point totals do not match with the Program Room and Stories grid page counts
JIRAALIGN-1914 The tooltip that displays when hovering over a team in the Team Load widget contains duplicate sprints. Resolving this defect also corrected calculation errors in the tooltip
JIRAALIGN-1241 Values displayed in the Team Load section of the Program Room use the incorrect calculation, ignoring override velocities entered for sprints

Note: This defect was previously reported as fixed in Release Notes Supplement for 10.75. Users reported the first fix did not resolve the issue, and a new correction was applied through the release of Team Load vs Capacity enhancements, detailed in this article
JIRAALIGN-1600 When viewing the unassigned backlog within the Feature Backlog page, the Pull Rank menu does not contain the option to use parent capability rank to sort features
JIRAALIGN-1904 Tag filters set on the Feature Backlog page are reset after changing the program increment selected in the Configuration bar
JIRAALIGN-1873 The menu that displays when attempting to add an expense from the Value tab of an epic’s Details panel is too small
JIRAALIGN-1845 The Epics and Capabilities grid pages display invalid results when filtering items in the Unassigned Backlog
Settings in the Setup Workflow window accessed from the More Actions menu are not retained on the Features grid page
JIRAALIGN-1828 The label indicating what filter is selected at the top of the Features grid page incorrectly displays Status when the page is filtered by State
The Agile by Group view on the Forecast page is confusing. Changed name to Agile by Program
JIRAALIGN-1904 The Configuration button displays an expanded menu section that does not change the display of the page
JIRAALIGN-1878 The % Capacity field contains a confusing tooltip
JIRAALIGN-1895 A 500 error displays when attempting to use the Sprints filter inside of the Advanced Configuration menu found in the Configuration bar
JIRAALIGN-1904 Accessing the Impersonate link from the User Menu results in a 524 error
JIRAALIGN-1855 The Roadmaps page fails to load and issues a 404 error if the program or portfolio selected contains more than 400 teams
JIRAALIGN-1849 Selecting a new option from the Sprint dropdown in the Team Room can result in a 504 timeout error
JIRAALIGN-1898 A 500 error displays when attempting to export the Timesheet Compliance report from Time Tracking
JIRAALIGN-1807 A 500 error displays when attempting to filter ideation users by ideation group on the Manage Ideation Users page
JIRAALIGN-1921 A 500 error displays when attempting to load data from the Test Sets page when more than 175,000 test sets exist
Program Board  
JIRAALIGN-1889 The planning issue alert message that displays on a feature card after removing a team’s story from the feature is misleading
Release Vehicles  
JIRAALIGN-1825 The Go Live Date and Closed/Cancelled fields inside of release vehicle Details panels do not work consistently
JIRAALIGN-1895 When viewing the Process Step Cycle Time report with a web browser configured to use dd-mm-yyyy date format, an invalid date range message displays
JIRAALIGN-1783 The Capacity Planning report erroneously includes days outside of a sprint when viewing remaining capacity hours
JIRAALIGN-1742 The Scope Change report displays canceled features that do not match the program specified in the Configuration bar
JIRAALIGN-1836 The Lead Time chart in the Lean Metrics pop-up window accessed from the Work in Process by State report labels the y-axis as Items instead of Days
JIRAALIGN-1774 The burndown charts in the Program Increment Progress report contain excessive open space on the x-axis
JIRAALIGN-823 The Roadmaps page does not retain selections made in the View Configuration menu
Strategy Room  
JIRAALIGN-1860 Chart labels are overlapped in the Snapshot Progress charts if lengthy custom terminology is set up for work items in Platform Terminology
Work Tree  
JIRAALIGN-1894 The Work Tree contains an invalid link named Program Increment Dashboard

The warning message that displays when attempting to access a canceled story states the item is in the recycle bin, instead of the canceled items bin

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.