Note: Due to a deployment issue with a previously reported feature, this article has been deleted and then republished. This method is used to provide notification emails to users subscribed to Release Notes updates. Please see the Team Room chart naming change section below for details.
The Atlassian Jira Align team is pleased to announce Jira Align v.10.101.
Enhancements and Features
These features for 10.101 were released to environments on the continuous release track on October 8, 2021, in version 10.101.0. The features will then be released to environments on the bundled release track on October 22, 2021, in version 10.101.2.
WIP limits for features in process steps (take two!)
Admins are once again able to enforce WIP limits on process steps for features, with an improved design! When creating or updating a process flow (Value Stream), there is now a field to enforce a count per process step. This count will enforce the WIP limit of features for that column.
This limit can be enforced for each program that the process step flow is assigned to on the process step’s Details panel.
Visualizing WIP limits on the feature backlog’s kanban view
On the feature backlog’s kanban view, as users drag and drop features to update them, the view will enforce these limits with a modal that notifies users when the WIP limit is exceeded.
When a WIP limit is set, the column will display the WIP limit on the right of the column’s header. When the WIP limit is exceeded for a column, the column’s header will turn red.
Note: There is a known issue in which the warning modal does not display and column headers are not updated when multi-program features are dragged and dropped.
Drag-and-drop functionality returning to the unassigned backlog
In a previous release, drag-and-drop ranking for most unassigned backlog views (meaning no program increment) was disabled to address a few known issues when ranking in those scenarios. This functionality has returned, so unassigned backlogs now support drag-and-drop ranking for all views.
New and updated Spend tab
Following the release of new financials earlier this summer, we’ve also updated the Details panels for epics, capabilities, and stand-alone features to better reflect financial values. The following changes have been made:
- Rename “Finance” to “Spend”: The Finance tab found in epic and stand-alone feature Details panels has been renamed to Spend, so as to further support the message that Jira Align is not a financial system of record. The Spend tab has also been added to Details panels for capabilities. All dollar calculations are intended to surface investment distribution for the purpose of making pivot / persevere decisions. The top of the new Spend tab for epics and stand-alone features is focused on the budget entered for the work item, and how much Accepted Spend has consumed that budget.
Note: To view the Spend tab for capabilities, you must switch on the Solution > Manage > Capabilities > Spend Tab permission toggle for your role.
- Progression of spend: Forecasted, Estimated, and Accepted Spend values provided by Jira Align are now visible from a work item’s Spend tab and can be clicked to launch the corresponding Spend Panel, to further dig into the details used to calculate financial values.
Note: The Progression of spend section is the only section that displays on the Spend tab inside of Details panels for capabilities.
- Other spend: Now, all financial input fields that existed on epic and stand-alone feature Finance tabs — with the exception of the Budget field — have been grouped under two new collapsible sections, Spend Risk and Other Spend, to make room for the progression of spend section.
Upcoming removals of legacy functions on Status Reports
While investigating defects related to the Status Reports page, we uncovered some legacy functionality that no longer operates correctly. In version 10.102.0, we plan to remove the following options:
- The Group by [Goal name] button found in the Extra Configs menu of a status report
- User profile bubble images that display on cards when viewing a status report for a portfolio or program
Delayed: Team Room chart naming update
Note: This feature was scheduled for version 10.101.0 but was not released due to a deployment issue. The feature was later released in version 10.102.0.
To provide better clarity and consistency across pages in Jira Align, we'll be updating a label name in the Sprint Status chart, accessed from the top of the Team Room. The Planned Velocity value will be changed to Committed Velocity, to better indicate this value is taken before the start date of the sprint.
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.
|JIRAALIGN-3402||Capability Split: Audit Log is empty||10.101.0|
|JIRAALIGN-3417||Displaying story's details view blocks its ordering in the Story Backlog||10.101.0|
|JIRAALIGN-3471||Backlog: Cursor should indicate that unassigned backlog cannot be sorted||10.101.0|
|JIRAALIGN-2221||Programs Setup: only super admins can see a solution type program||10.101.0|
|JIRAALIGN-3242||HTML formatting not showing correctly in the acceptance criteria field in feature within WIP by state report with ADO||10.101.0|
|JIRAALIGN-3130||Record Status card: Objective title should wrap in the respective column not to cause the other columns misplacing||10.101.0|
|JIRAALIGN-3539||Notification/error message in the checklist is in black font on black background||10.101.0|
|JIRAALIGN-2145||Checklists: Unable to launch Google page from a Check List Item||10.101.0|
|JIRAALIGN-3541||Forecast -> Plan Capacity -> 'Current FTE' calculation is considering deactivated users.||10.101.0|
|JIRAALIGN-3543||Program Increment: Jira Align Kicks Users Out When Clicking Save (Can't Add Programs, blocking new AgileTeams)||10.101.0|
|JIRAALIGN-3384||Effort Points Burndown: Inconsistent naming||10.101.0|
|JIRAALIGN-3646||Objective/OKR: Old OKR/Objective experience is defaulting the field Status to Off Track instead of Pending||10.101.0|
|JIRAALIGN-3572||Integration: Error when adding new Project with same Project Key from different Connector||10.101.0|
|JIRAALIGN-3519||Wrong Default User in Jira Settings breaks Features in Canceled Bin when Canceling from Jira||10.101.0|
|JIRAALIGN-3607||Status Report - Program: Capture is cropping too high||10.101.0|
|JIRAALIGN-3609||Viewing detailed timesheet for some users fails||10.101.0|
|Roadmap: Feature by Epics - All Kanban teams IDs in the instance are retrieved when expanding Feature||10.101.1|
|N/A||Jira Connector: Connector Splunk logs include email addresses||10.101.2|
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.