Release notes for 10.131.X


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

Note: This article has been republished. This method is used to provide notification emails to users subscribed to release notes updates. We've updated this article to include notice of the future end-of-support status and removal for mind maps

The Atlassian Jira Align team is pleased to announce Jira Align v.10.131

Enhancements and features

These features for 10.131 were released to environments on the continuous release track on March 15, 2024, in version 10.131.0. The features will then be released to environments on the bundled release track on March 29, 2024, in version 10.131.2:

Try the new Risk ROAM report

We’ve enhanced and modernized the look and usability of the Risk ROAM report.


Contact your Advisory Services representative or open a ticket with Atlassian Support to enable a preview of the new version in your sandbox environment. You can request the preview in production environments as of the 10.131.2 release. We plan to enable the preview for all instances in the 10.134.X releases, which will deploy in June 2024. If we see wide adoption of the preview, we may accelerate this schedule.

Once the preview is enabled, switch on the New experience toggle at the upper-right corner of the page to use the new version of the report. You can switch between the new and legacy experiences for an extended time.

Modern look with drag-and-drop functionality

The new risk ROAM report provides an updated look, using columns that represent each risk ROAM status, similar to a kanban board. You can drag-and-drop cards between columns to change risk status and reorder risks visually.

Alternatively, you can use the the three dot (…) menu found on each risk card to move between columns and change vertical position.


New filters and controls

We’ve added new filters and chart controls to a consolidated View settings menu. In addition to filtering risks by a relationship to work items, you can now filter risks by the Occurrence and Impact fields.


Use the toggles at the bottom of the menu to control which charts display.


The new experience provides better accessibility for all users, meeting Atlassian’s raised standards for new functionality. The report supports keyboard navigation and screen readers, including the three dot (…) menu found on each risk card.

New navigation menu improvements

  • Caching was introduced to reduce the number of calls required to load the top navigation bar and sidebar. As a result, the time it takes for pages to become interactive was reduced.
  • We updated the Strategy menu in the top navigation bar so that you no longer need to select a strategic snapshot. Now, selecting the Strategy menu will automatically open the strategy room.
  • The strategic snapshot filter was removed from the sidebar since it only applied to a few pages on this menu state. Pages that required a strategic snapshot now have a page-level strategic snapshot filter. As a result of these changes, you no longer need to grant additional permissions to users who require access to global views of roadmaps and the backlog.

New portfolio room role permission to control access to financial information

A new system role permission was added to control access to the Financials tab of the portfolio room. This permission will be on by default for users who already have the portfolio permission turned on. Turning off the permission will mean that users will not see the Financials tab. This permission can be found under Portfolio > Portfolio > Portfolio Room > Financials tab.

Removal of legacy reports

As previously announced, we’ve removed 39 legacy reports:

  • Agile added/dropped objects
  • Card movement
  • Control chart
  • Cumulative counts
  • Demand vs capacity by asset
  • Effort point burndown
  • Hours by team
  • In-progress trend
  • Metric report
  • Plan by quadrant
  • Points delivered by type
  • Points planned vs points accepted
  • Portfolio quality tracking
  • Planned vs earned velocity
  • Program dashboard
  • Program increment confidence report
  • Program increment countdown
  • Program increment sprint report
  • Program increment status/Program increment status summary
  • Program increment tree map
  • Progress by product
  • Program increment/sprint metrics
  • Split analysis/Split story analysis
  • Sprint coverage/Sprint story coverage
  • Sprint hours/Sprint performance
  • Sprint snapshot
  • Status of team experiments
  • Story completion ratio
  • Story LOE
  • Story points ratio
  • Stories by state (PIs)
  • Team emotion (by sprint)
  • Team goals
  • Team member allocation
  • Team states/Sprint states
  • Value delivered
  • Velocity variance
  • Work in progress
  • Work summary

Sync business driver, capitalized, and category fields with the Jira connector

Field management tab with business driver, capitalized, category fields.png

Jira Align now supports bi-directional syncing of the Business Driver, Capitalized and Category fields. Changes include both syncing ability (we didn’t sync those previously) and the ability to map the fields on our new field management tab.

This is a feature-toggled functionality that is turned on by default. To hide this feature in your instance, reach out to our Support team.

Why? details and work code field mappings moved to Field mapping tab

In the Jira connector, both the Why? details and Work code fields are now available on the Jira connector’s field management tab.

Rich text editor on the description field for epics and capabilities

In version 10.130, we announced rich text editing in the description field for epics and capabilities. This feature has now been turned on for everyone.

API 2.0: Improved performance to reduce SQL timeouts

Our existing construction of paginated queries in the shared data layer was sub-optimal and caused performance issues and SQL timeouts at high data volumes. To resolve this issue, we made a structural change to the query that significantly improved performance and reduced the incidence of SQL timeouts.

API 2.0: Queries for users now respect permissions

We’ve updated the API 2.0 to only show the following five properties when expanding a user object:

  • id
  • uid
  • email
  • First Name
  • Last Name

Previously, all user properties were accessible when querying for owners, regardless of permissions. To see all available user properties, you can query the Users API from an account that has sufficient permissions to view user details, and/or the work item where the user is set as the owner.

End-of-support status and future removal of mind maps

Mind maps will no longer be supported as of version 10.134.0, scheduled for release June 7, 2024. After this date, we'll no longer file new defects related to mind maps, and the functionality will be considered for removal later in 2024. We'll provide at least 30 days advance notice through future release notes.

Mind maps allows you to create a visual map that represents a work hierarchy. If you'd still like to create and share visual maps, consider trying Confluence Whiteboards, which offers many more editing and linking capabilities. 

Defect fixes

The list of defect fixes will be updated to reflect changes in weekly maintenance releases. You can see the contents of individual maintenance releases in the Supplemental Release Notes section.

Key Summary Release Version
JIRAALIGN-4839 Process Steps - Changing process step to "Select One" is not being recorded in the audit log 10.131.0
JIRAALIGN-5183 Scrum Master Role unable to create Acceptance Criteria during locked sprints 10.131.0
JIRAALIGN-5322 New navigation - Strategic snapshots and backlog doesn't seem to be available to all users 10.131.0
JIRAALIGN-5358 New Nav: filter for "Primary Program" is auto-selecting the program selected in the sidebar menu (but its not impacting the work items shown) 10.131.0
JIRAALIGN-5378 Creating Stories in JA from Jira Connector Results in Automation Field Set to 0, While UI-Created Stories Have NULL Value 10.131.0
JIRAALIGN-5795 API - API allow to use archived Program increment on Epics/Themes which is not allowed in the UI 10.131.0
JIRAALIGN-6269 Newly created Dependency custom field is not displayed on the "Add Dependency" slide-out. 10.131.0
JIRAALIGN-6323 Portfolio Epic's inProgressDate API property not set when child Feature moves to "In Progress" 10.131.0
JIRAALIGN-6345 Portfolio status report - Changing the health colors increases the icons size 10.131.0
JIRAALIGN-5310 Epic Grid - Parenting Features to Epics when capabilities are enabled breaks the Epic Grid 10.131.2
JIRAALIGN-6290 Unable to attach Themes to Objectives through objectives creation panel 10.131.3
JIRAALIGN-6583 OKR slideout: parent KR alignment is not removed from DB when changing parent via API. 10.131.3
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.