Release notes for 10.122.X

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

• Enhancements and features
• Defect fixes

Enhancements and features

These features for 10.122 were released to environments on the continuous release track on July 7, 2023, in version 10.122.0. The features will then be released to environments on the bundled release track on July 21, 2023, in version 10.122.2:

New navigation

We are excited to share that our new, improved navigation experience is now available!

With this release, administrators can turn on a general platform setting that will allow users to opt-in to the new navigation experience.

When the Enable New Navigation setting is set to Yes, users will be able to switch to the new experience with a simple toggle in the current Configuration bar. Then, from any page, you can use the same toggle to switch back to the old experience.

With the new navigation, you’ll get:

1. A new information architecture that orients new and existing users on what you already know - your teams and team rooms.
2. A new top navigation bar that moves from a model where users primarily navigate views to one where you navigate team or product hierarchies.
   
   
3. A new sidebar to improve the discovery of views that allow users to accomplish their top tasks. As you navigate across pages, your views will stay filtered by the selected scope and time period. We also reorganized links to key features. Under the More items section, you’ll find item grids where you can create and manage epics, features, stories, objectives, dependencies, and more. Reports includes reports that apply to your selected scope and time period. And More pages includes non-grid and non-report pages like meetings, assessments, and framework maps.
   
4. A new homepage that provides quick access to the rooms and starred pages that are most important to you.
5. In-product guides to quickly onboard you to the new navigation experience.

For more information, including a timeline for the complete rollout, check out our Community post (it’s also a great place to ask questions).

Forecated Spend for features

Now that you can use the forecast page and Details panel tab with features, you’ll likely want to see how those estimates translate into potential costs. That’s why we’ve added the Forecasted Spend financial value to features. Forecasted Spend for a feature is calculated as:

(Program estimate entered on the Forecast tab) * (Program Spend per Point)

If the feature is associated with more than one program, the result of the calculation from each program and the corresponding Program Spend per Point will be summed. Additional programs must be associated with the program increment the feature is assigned to in order to be visible on the Forecast tab and included in the total Forecasted Spend.

You can view Forecasted Spend values for features from multiple locations:

• Portfolio Room, using the Financials view
• Status Reports, using the Financial view
• Forecast page
• The Spend tab of a feature’s Details panel

Selecting a value from any of these locations will load the feature’s Forecasted Spend panel, which provides a breakdown of what estimates and spend per point values factor into the calculation.

Backlog: Updated estimated program PI load calculations

As part of adding forecasting abilities to features, we’ve updated the Estimated Program PI Load bar’s calculation, which is found on the Kanban > Column View of feature and epic backlog pages.

Previously, this calculation used the estimate found on the Details tab of a feature’s Details panel, while calculations for epics and capabilities used program estimates found on the Forecast tab of Details panels. Now, program PI load calculations for epics, capabilities, and features all use program estimates from the Forecast tab. This provides you with consistency when forecasting work for a program and PI combination.

When using the Card Size > Normal View option, feature cards will now display the program estimate entered on the Forecast tab in either member weeks, team weeks, or points, depending on the estimation system selected for the portfolio. If the portfolio estimates in t-shirt sizes, no value will display on the card.

ADO connector custom single-select dropdown field sync

Building off of the previous release, the Azure DevOps connector will now also support the sync of Jira Align single-select dropdown-type custom fields for features and stories. This data can be synced bidirectionally or from ADO to Jira Align only, depending on the sync direction configured for a corresponding work item type.

This feature is aimed to enable the sync of critical data between Jira Align and ADO. Also, it will improve the experience by syncing some required ADO fields that couldn’t have been synced earlier and, potentially, unblock the ability to use bidirectional sync.

Existing system fields configured in Administration > Settings > Details Panel Settings will display on the ADO connector slide-out in the corresponding work item sections.

To make data sync, you’ll need to enter the exact name of the needed ADO field in the mapping text box. The system doesn’t enforce users to map any specific ADO field type. Data from Jira Align text input fields can bidirectionally sync with ADO text, picklist, boolean, and numeric fields.

If a Jira Align custom field is not turned Active for any of the portfolios whose child programs are mapped in your connector, a warning icon will be shown next to this field mapping on the connector slide-out panel. Make sure that the custom field is activated for the needed portfolios. This will allow you to see the field on Details panels of individual work items and have the data synced by the connector.

Jira connector settings renaming

To resolve JIRAALIGN-4904 and JIRAALIGN-3886, we renamed two Jira connector settings to better describe their behavior:

• Create sprints in Jira Align from Jira has been renamed to Sync sprints from Jira
• Default Jira Align story priority has been renamed to Default Jira Align story and feature priority

Health and Status added to Epic API

The Epic API GET method will now return the Health and Status values from the epic status report in the JSON response.

Quality module: Upcoming removal of test folders and builds

In version 10.121.3, we removed the summary pages within the Quality module, while references to some objects remained. In upcoming versions, we’ll be cleaning up the codebase and removing references and links to the following objects:

• Builds: removal scheduled for 10.123.0
• Test folders: removal scheduled for 10.124.0

Work in progress by step: Stats tab enabled by default

To provide more information when you visit the work in progress by step report, we’ve switched on the Stats toggle by default. When enabled, the toggle displays the throughput, efficiency, and cycle time from the past 30 days underneath each work item section.

If you switch off the toggle, your selection will be retained the next time you visit the report.

Clear access to Atlassian's Privacy Policy

To make in-product help and required privacy policy information accessible for all users, we have disabled the setting to remove the Help button. The setting, called Show “Help” Button, is visible from the general platform settings but has been set as read-only. The setting will be removed in a future release.

In addition, we’ve added a new security setting that allows customization of the privacy policy URL. Setting a Privacy Policy URL value will edit the link users access when they select Privacy Policy in the Help slide-out.

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.