Note: This article has been republished. This method is used to provide notification emails to users subscribed to release notes updates. This article has been updated to change the release version of the removal of Quality module summary pages. After further consideration, we will be delaying the removal of the pages to version 10.121.3.
The Atlassian Jira Align team is pleased to announce Jira Align v.10.120.
Enhancements and features
These features for 10.120 were released to environments on the continuous release track on May 12, 2023, in version 10.120.0. The features will then be released to environments on the bundled release track on May 26, 2023, in version 10.120.2:
Upcoming removal of Quality module summary pages
In version 10.121.3, we’ll be removing 15 pages that make up the Quality module from Jira Align. The Quality module is a legacy set of features that were built for team-level testing and QA activities. After careful consideration, we’ve decided to remove these functions so that we can focus on the primary goals and functions of Jira Align.
This first step will be focused on removing the summary pages within the Team > Quality navigation menus. We will not be removing objects like test cases or acceptance criteria, nor the ability to view objects within work item Details panels in version 10.121.3. We will announce the timing for removing the objects and functionality in a future release.
Pages that will be removed:
- Acceptance Criteria
- Build Streams
- Last Build Status per Release
- PI Test Plan
- Sprint Plans
- Test Cases
- Test Environments
- Test Folders
- Test Plans
- Test Sets
- Test Suites
- Testing Board
- Testing Room
System role permission toggles related to these pages will also be removed from Admin > Roles.
Note: The Defect Suites page will be moved to the Manage section of our Navigation menu.
If you have used this functionality in the past, we encourage you to migrate your testing and QA practices to Jira Software. The Atlassian Marketplace has several offerings that can enhance your Jira environment with customized testing functionality.
If you would like to save a record of these pages, you may do so before the release of version 10.121.3. You can use screenshots and Save options from your browser to capture the contents of an accessible page. You can also use the Export option found under the More Actions menu on the Test Cases page to make a record of your test cases.
Upcoming removal of 21 reports
In version 10.123.0, we’ll be removing 21 legacy reports from Jira Align.
After reviewing recent usage data, it became clear that this functionality was not providing significant value. Some of these reports were not fully developed or were made inaccessible during our transition from Jira Align version 9X to 10X. By removing these reports and streamlining our codebase, we’ll have more capacity to address defect fixes across the product. These changes will also reduce our testing overhead, which will allow us to build and ship enhancements more rapidly.
Reports that will be removed:
- Budgetary Tracking
- Simulation Forecast
- Automation Trend (Stories)
- Automation Trend (Acceptance)
- Override Events
- Scorecards and Scorecard Details
- Sprint Defect Trend
- Rate of New Cards Added
- TP to WIP Ratio
- Enterprise Balanced Scorecard
- Group KPIs*
- Individual KPIs*
- Find Fix Rate
- Today's Plan
- WIP Limit Infractions
- QA Availability
- Defects By Priority
- Defects By Story
System role permission toggles related to these pages will also be removed from Admin > Roles.
*Note: For a short time after these removals, previously created KPIs will continue to display on the Operational Excellence Vision report.
If you have used this functionality in the past and would like to make a record of your entries, please visit the reports prior to version 10.123.0 to archive your data. You can use screenshots and Save options from your browser to capture the contents of an accessible report.
OKR hub: column reordering
To better customize the OKR hub for your needs, you can now reorder the columns on the OKR hub. All columns except the Summary column are repositionable. To move a column, drag and drop it into place.
Azure DevOps Connector: changes on the connector slide-out panel
In order to clean up unused settings and reduce unnecessary manual setup of the connector, we've introduced some minor changes to the ADO connector slide-out panel. These changes don’t have an impact on connector functionality and don’t require any additional actions from your side.
Some settings that are no longer used by the connector are now hidden. These are three settings from the General tab of the connector slide-out panel:
- Internal log level: Splunk shows Errors/Warnings/Information logs automatically.
- Time zone: Time zone is picked up by the connector automatically.
- Instance image URI: The image used for the link button on work item details panels is stored.
Additionally, Scope Path setting on the Projects tab will be hidden for connectors using multiple projects (when Support Multiple Projects is set to True). This setting is applicable only when single-project mode is used.
Some work item-related settings have been moved to a new General section of the Items tab:
- Default Sync User
- Enable Removed State
- Add Hyperlink to ADO
- Initial Sync Date from ADO
For newly created connectors, we’ve changed default values for two settings:
- Support Multiple Projects will be set to True as this mode is used by most of our customers.
- Delete action for all work item types will be set to Move to recycle bin.
Jira Connector: improved warning messages on the board mapping table
In the scope of the fix for JIRAALIGN-4576, we improved the warning messages on the board mapping table. Now, if a board’s associated project(s) are removed from the project mapping table, a warning icon will be listed next to the board letting you know that no project could be found.
In addition, we added a warning modal when removing a project mapping letting users know that board mappings are not automatically removed.
Misaligned story count correction on Program Increment Progress report
While reviewing the logic of the charts found on the Program Increment Progress report, we improved the handling of misaligned stories. Previously, if a story was assigned to the PI being viewed on the report, but was associated with a feature that was assigned to a different PI, the story’s points would still be counted in the Program Increment Burndown by feature and Program Increment Burnup by feature charts. Now, the feature-based burndown and burnup charts will only show aligned story points: A feature must be assigned to the PI being viewed, and then child stories assigned to the same PI or unassigned backlog will be included in the chart. Child stories assigned to a different PI will not be included.
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-3366||Jira connector Logs vanish when changing the days or type of logs||10.120.0|
|JIRAALIGN-3443||Incomplete Kanban Team Stories do not appear in PI Cleanup report||10.120.0|
|JIRAALIGN-3611||Process step tool tip on Theme incorrectly refers to Epic||10.120.0|
|JIRAALIGN-3690||Theme: Character length field validation limits the number of Programs and PIs that can be added to a Theme||10.120.0|
|JIRAALIGN-3797||Removing Jira Align Issue tags are not removing Jira Labels||10.120.0|
|JIRAALIGN-3922||Landing on Work in Progress by State report doesn't initially load anything||10.120.0|
|JIRAALIGN-4385||Colour codes on identical Tags is not maintained when Epic is Copied||10.120.0|
|JIRAALIGN-4433||Large quantity of misaligned stories cause Program Room interaction to slow down/hang||10.120.0|
|JIRAALIGN-4466||Feature summary field needs UI validation to be < 255 characters||10.120.0|
|JIRAALIGN-4576||Jira board still available after delete the Jira Project on Jira Align||10.120.0|
|JIRAALIGN-4625||Importing namesake work items silently fails, rendering no results and no messages in UI||10.120.0|
|JIRAALIGN-4724||Team Room does not show Defect icon as it is shown on the Program Room||10.120.0|
|JIRAALIGN-4732||API 1.0: PUT request fails on users endpoint if "TeamRoleId"=-1||10.120.0|
|JIRAALIGN-4742||API - Reactivating a user that was deactivated a long time ago produces error 400 - UserEndDate cannot be set before 1 days in past.||10.120.0|
|JIRAALIGN-4802||New sprint mapping : The state of the Jira sprints is not synced||10.120.0|
|JIRAALIGN-4807||API 2.0: DTO fields not always set in JSON response for Objectives/Milestones endpoint||10.120.0|
|JIRAALIGN-4812||Members of Agile Teams being added without logging in Audit log||10.120.0|
|JIRAALIGN-4817||Jira management settings>Jira Align Sprint: Save button clears existing mappings||10.120.0|
|JIRAALIGN-4861||InProgressDate on Epic via API only shows date if moved to in progress by story||10.120.0|
|JIRAALIGN-4862||Epic API inProgressDate not changed when reset by feature changing to in progress||10.120.0|
|JIRAALIGN-4868||"Sprints are not mapped in calendar order" warning still displays after 'end-date' based sprint mapping logic is enabled||10.120.0|
|JIRAALIGN-4886||New Objective Experience Showing Deleted Features||10.120.0|
|JIRAALIGN-4934||Jira Projects that were assigned process steps pre-10.117 have process step toggle inverted.||10.120.0|
|JIRAALIGN-4823||Attempt to import Epics results in HTTP 500 error||10.120.1|
|JIRAALIGN-5013||ADO Connector - Jira Align Story receiving wrong State after syncing with ADO||10.120.2|
|JIRAALIGN-4884||Editing a Program Increment when you do not belong to the saved portfolio allows you to change the portfolio||10.120.3|
|JIRAALIGN-5018||Team Room: Impediment cards only display Story Impediments||10.120.3|