Release Notes for 10.83


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

Enhancements and Features 

Team Room Progress card enhancements for Agile teams

We’ve updated the dials found within the Progress card of the Team Room, for Agile teams:

The middle dial has been renamed Sprint Load to more accurately reflect the dial’s displayed percentage. We also updated the hover tooltip that explains the calculation. Sprint Load is calculated as:

((Sum of level of effort (LOE) story points assigned to the sprint) / (Average Team Velocity)) * 100


To help you reference the team’s average velocity, we replaced the right-side Accepted dial with Average Team Velocity. This visibility should equip you and others to quickly sense the probability of finishing all work planned in the sprint.


If you’ve entered an override velocity for the sprint, we’ll show that value instead of an average, with an Override Team Velocity label.


To see how your Average Team Velocity or Override Team Velocity is calculated from the last five completed sprints, click the number displayed below the label. The team’s Details panel will display, with the sprints used to calculate the average highlighted.


Report calculation and consistency changes

We’ve updated several report names, calculations, and labels to provide more consistency across views of similar data. Changes include:

Group Velocity (also known as Program Increment Velocity):

  • The report name changed to Points Accepted (by Sprint)

    • Because no point totals are divided by a unit of time, this report doesn’t reflect a velocity value

  • We changed the Velocity label in the legend and hover messages to Points Accepted

  • We ensured the chart uses the same calculations as the Portfolio Program Predictability report, to resolve defect JIRAALIGN-1525

Sprint Coaching:

  • We updated the names of several categories found in The Committed Plan section, to better reflect their purpose. No changes were made to how these values are collected:

    • Committed Work label renamed to Stories Committed

    • Task Breakdown label renamed to Tasks Committed

    • Total Effort label renamed to Points Committed

    • Total Value label renamed to Value Points Committed

    • Acceptance label renamed to Acceptance Criteria Committed

  • We updated some label names within The Statistics section:

    • In the burndown chart at the top of the section, the orange Actual Burn line changed to Hours Remaining

    • We changed the Sprint Story Progress progress bar at the bottom of the section to Sprint Progress

    • We renamed the Velocity chart at the lower-left to Points Accepted by Sprint, and added an Average team velocity indicator to the chart

    • We resolved some issues with the Rate of Completion chart

      • Dev Complete label renamed to Dev Tasks Complete

      • QA Complete label renamed to QA Tasks Complete

      • The chart now correctly displays the number of development tasks and QA tasks completed each day

Sprint Metrics (also known as the M1 Report):

  • We removed the % symbol from the chart name at the top of the page, and connected the first word to Platform Terminology settings. For example, if you have customized your Sprint term to be called “Iteration”, the chart name will read “Iteration Metrics”.

  • We updated the Team Objectives section to show a percentage of team objective completion. Added a tooltip explaining how the percentage is calculated. Each cell is calculated as:

    • ((# of team objectives completed) / (# of team objectives planned)) * 100

  • We updated the Team Defects section to display white cells with a - symbol when there are no open defects in a sprint, instead of a red cell with a ? symbol

  • Story Completion section renamed to Stories Committed vs Accepted

  • Planned vs Accepted section renamed to Points Committed vs Accepted

  • Splits & Drops section renamed to Split and Dropped Stories

Velocity Trend (Planned vs. Actual Velocity Variation by Team):

  • The report name changed to Story Point Progress by Team

  • We changed the display style from a single bar showing planned points with a dot inside/above the bar showing accepted points to a dual-bar graph: blue bars represent points planned, while green bars represent points accepted

  • We renamed the chart header to Variation between Planned and Accepted Points by Team

  • We renamed the chart subheader to See the variation between a team’s planned and accepted points during the program increment to identify predictable teams and spot negative trends before they become a problem


Program Predictability Report:

  • We moved the program comparison chart from the bottom to the top of the page

  • We moved the Tier view dropdown from the Extra Configs menu to its own space in the upper-left corner of the report

  • We ensured that calculations done by the charts are correct:

    • Planned Objectives are critical path objectives assigned to the team or program

    • Delivered Objectives are both critical path objectives and stretch goal objectives assigned to the team or program, and marked Complete

    • Objective Progress percentage values are calculated as: (Delivered Value / Planned Value) * 100

Progress by Objective:

  • We reviewed and updated calculations done by the report to ensure that:

    • Planned Objectives are critical path objectives assigned to the team or program

    • Delivered Objectives are both critical path objectives and stretch goal objectives assigned to the team or program, and marked Complete

  • We added an info message to the top of the page explaining that planned values do not include stretch goal objectives

  • We added tooltips to planned and delivered value labels

Program Allocation:

  • We moved the Program Totals section to the top of the page

    • Added a row to the section displaying counts of accepted points

  • Loaded labels renamed to Points Accepted

  • Actual labels renamed to Points Accepted

Team Burndowns:

  • We corrected the x-axis of the charts to show the time period of a sprint, +/- 1 day

  • Planned Velocity label renamed to Points Planned

  • Accepted Velocity label renamed to Points Accepted

  • We shortened chart headers for better readability

  • We re-ordered the legend at the bottom of each chart to match the display of other burndown charts

Configuration bar filtering: Objectives

The Objectives and Objective Backlog pages now have been updated to correctly support more scenarios where different filters are selected in the Configuration bar:

  • Product has been disabled as an option, as it does not apply to objectives

  • When an organization structure is selected in the Configuration bar, objectives are shown when the owner is a member of the selected structure or child levels of the structure

  • When a release vehicle is selected in the Configuration bar, objectives are shown if they are associated with a feature assigned to the release vehicle

Configuration bar filtering: Defect Backlog

The Defect Backlog page has been updated to correctly support more scenarios where different filters are selected in the Configuration bar:

  • When a product is selected in the Configuration bar, defects are shown when their parent feature (via a defect-story-feature hierarchy) is associated with the selected product or child products

  • When an organization structure is selected in the Configuration bar, defects are shown where the user specified in the Assigned to field is a member of the selected structure or child levels of the structure

  • When a release vehicle is selected in the Configuration bar, defects are shown that are directly assigned to the release vehicle

Defect Fixes

JIRAALIGN-1966 Users receive a Whoops error and SQL timeout when searching the Stories page
JIRAALIGN-2106 On the Kanban Boards page, an internal server error occurs when clicking on links to open Details panels
API 2.0  
JIRAALIGN-2215 When a user is updated via patch, the user loses their API token
JIRAALIGN-2133 When creating a release vehicle using API 2.0, users can't easily figure out the right status and health because the logic behind the Health field is dependent on the selected state
JIRAALIGN-1957 PrimaryProgram object is missing from GET ​/align​/api​/2​/Epics results
JIRAALIGN-2175 The API 2.0 documentation contains an incorrect response code 200 for the Release Vehicle post request
JIRAALIGN-1664 Organization Structure doesn't appear in Products GET and can not be set with Products PUT/POST
JIRAALIGN-2141 Endpoints return all records regardless of the portfolio or program assigned to the API user
JIRAALIGN-2138 In hierarchies with capabilities enabled, epics are not set to In Progress when a grandchild feature is set to In Progress
JIRAALIGN-2137 The list of impediments is not filtered by program and PI on the escalation's Details panel
JIRAALIGN-2136 The Escalations page is not filtered by Configuration bar selections
JIRAALIGN-2173 When applying filters, the 'not equal' (≠) character displays as an 'equals' (=) sign
JIRAALIGN-2223 Total Budget (Epic Level) in the Themes export contains incorrect values
JIRAALIGN-2031 The import fails (times out) at 100 seconds when importing a JET export file
JIRAALIGN-1928 Owner field does not recognize user emails when mass updating using an import
Jira Connector  
JIRAALIGN-1419 On the Jira Boards tab in Jira Management, filtering by Board ID on some boards cannot find the desired board
Mind Maps  
JIRAALIGN-1673 Capabilities cannot be displayed on mind maps, even in hierarchies with capabilities enabled
JIRAALIGN-801 Users can't delete dates on objectives once the target date, ask date, and completion date are selected
Program Room  
JIRAALIGN-2189 The tooltip on the misaligned section contains inaccurate information
JIRAALIGN-2147 The full report for the Program Room's Program Increment Burnup is not based on the selected program
JIRAALIGN-2187 Program Room and Story Backlog use different icons for stories that have the Defect type
JIRAALIGN-2089 Feature titles are truncated at 1/3 of the available column width
JIRAALIGN-1231 In the Scope Change report, removed features do not display
JIRAALIGN-1525 The Portfolio Program Predictability report and the Group Velocity report use different formulas
JIRAALIGN-2203 The Epic Analytics report does not reflect Platform Terminology settings
JIRAALIGN-1470 In the Progress by Objective report, filtering by theme doesn't apply any filters
JIRAALIGN-2202 Supporting capabilities aren't displayed on the Work in Process report
JIRAALIGN-1314 In the Trace report, users experience a gateway time-out when attempting to trace an epic with large amounts of associated items
JIRAALIGN-2191 When updating a story, the audit log shows a Jira Project change being updated to null, even when the Jira Project field has not been modified
JIRAALIGN-651 No warning displays when users attempt to delete teams that have sprints assigned
JIRAALIGN-2142 There is no option to filter by Active status
JIRAALIGN-2176 Adding the Strategy Tree page to the Favorites list adds the page to the list with an incorrect title
JIRAALIGN-2228 The user profile image on the home page is distorted
JIRAALIGN-1569 The pencil icon to edit work item titles does not display on the Details panel for MacOS users
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.