The Atlassian Jira Align team is pleased to announce Jira Align v.10.129.
Enhancements and features
These features for 10.129 were released to environments on the continuous release track on January 19, 2024, in version 10.129.0. The features will then be released to environments on the bundled release track on February 2, 2024, in version 10.129.2:
Reminder: The transition to new navigation begins soon
One month prior to the removal, users will be notified with updated in-product guides, similar to this:
For example, if your instances will transition during the 10.130.X releases, your sandbox environment on the continuous release track will see this notification on Friday, February 9, letting users know old navigation will be removed on Friday, February 23, in the 10.130.1 release. Your production environment on the bundled release track will see a similar notification on Friday, February 9, but it will notify users that old navigation will be removed on Friday, March 8, in the 10.130.3 release.
- If you’ve already reached out requesting more time before old navigation is removed, your instances are currently planned for transition in the 10.132.X releases.
- If you’d like to remove the old navigation menus and homepage now, please submit a support ticket or reach out to your Advisory Services representative.
Continued changes to on-premise backoffice service
As of version 10.127.X, the on-premise backoffice service does not connect to the AgileCraftServer database, which is no longer supported for use. We have been monitoring and performing testing to ensure that this change has no unintended effects.
In version 10.129.X, the AgileCraftServer database is no longer needed:
- New installations will no longer need to create AgileCraftServer.
- Existing installations should run a command to rename AgileCraftServer, and revoke access for Jira Align SQL users.
- The renamed AgileCraftServer DB can be dropped when no relevant data is needed.
We are currently updating our installation and upgrade instructions to account for this change, in both the on-premise guide and release notes included with the on-premise download package. If you have questions about working with the backoffice service or databases, please contact Jira Align Support.
Jira connector: Field management tab improvements
We have added a visual indicator for the sync direction of each field mapped in the Field management tab. This indicator will display one of three sync directions:
- Jira to Jira Align
- Jira Align to Jira
In addition, a new field mapping is now available in the Field management tab: feature points. Its sync directionality can be changed by selecting the sync direction button.
The other field mappings will display sync directionality but are not editable, and follow the sync direction of the work item itself.
Note: The sync direction for feature fields is set by Allow feature sync from Jira Align to Jira setting on the Jira Setup tab. Make sure to select the desired option on the Jira Setup tab before mapping the fields here.
Azure DevOps connector: new warning message on stories out of sync
Stories that previously synced with Azure DevOps, but were removed from the connector story type mapping will now display a warning message on the story details panel.
Quality module: Confirmed and upcoming object removals
In version 10.121.3, we removed the summary pages within the Quality module, while references to some objects remained. In this release, we’ve cleaned up the codebase and removed all references and links to test cases.
In version 10.130.0, we plan to complete our work, and fully remove all database backup tables for any quality pages and objects.
Note: Acceptance criteria entries remain available in work item details panels. There is not a plan at this time to remove this functionality.
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.
|API: updates with API to Features fails if the Portfolio has Process Step as required but the Program doesn't have one associated
|Program Increment Progress report (PIP) - Drill Down Burnup predicted line calculating incorrectly
|When deleting a Story in Jira the connector will not clear key fields as it does when Story is deleted in Jira Align
|Teams: Agile Team Member List has Program Team Members Included
|The inconsistent behavior of the SAVE function being available for the Feature work item which is different than what is observed in the other work items
|Kanban Boards: Lean Metrics are not capturing correctly the number of cards
|Platform Terminology changes for Dependencies and Teams Not Reflecting in Relationship Trace and Status Report Pages
|Can't create feature from epics slide-out panel without add epics permission
|No logging for Success Criteria PI change
|Risk Grid : "Relationship" column does not honor Platform Terminology settings
|Adding/Removing Teams on the User's record doesn't update Audit Log
|<On-Prem> Atlassian Cloud Terms of Service acceptance message is displayed on Login and reset password page
|Jira Product Mapping returns 500 error when value is greater than 50 characters
|Program Tracking Report does not honor Configuration Bar filters for Dependencies
|API - /rest/align/api/2/features filter by Parent ID with more than 20 entries in the result set not handled correctly
|Program Increment Progress - Charts are not being fully rendered
|New Nav - Features grid without filters cannot be starred
|ADO connector deleting hyperlinks when JA syncs with the Story/Features
|BuildFeatureWhy - DetailsNullable object must have a value
|Forecast view doesn't show all the Features
|ADO connector - Unable to sync new work items under Story Type with Task enabled
|BuildFeatureWhy triggering deadlocks on Jira Align database