The Atlassian Jira Align team is pleased to announce Jira Align v.10.103. Please note that the 10.103.0 feature release was not deployed, as our developers worked to resolve critical defects found in the build. As a result, the feature release for 10.103 is version 10.103.1.
Enhancements and Features
These features for 10.103 were released to environments on the continuous release track on December 10, 2021, in version 10.103.1. The features will then be released to environments on the bundled release track on December 17, 2021, in version 10.103.2:
Improvements in syncing release vehicles with fix versions
We’ve added a new way that release vehicles are synced between Jira Align and Jira. Previously, changes to release vehicles were only synced to Jira when work items were updated.
Now, in addition to work item updates, we’ll sync release vehicles to Jira independently, based on the Timer on continuous push to Jira setting.
The scope of this work resolves several JAC defects: JIRAALIGN-3037, JIRAALIGN-3525, JIRAALIGN-3099, JIRAALIGN-818, and JIRAALIGN-1348. We’re planning to resolve additional defects around bi-directional release vehicle syncing in the future, so stay tuned!
Ranking enhancements and improvements
For ranking items to and from external systems, when an issue or work item doesn't exist in either Jira or Jira Align, the rank is now updated accordingly and the proper error is logged in Splunk.
We also added a multi-connector sync to push and pull ranks for multiple Jira connectors at the same time.
Updates to syncing sprints with Azure DevOps (stories and defects)
Previously, the connector would set the sprint in Azure DevOps to the first ADO sprint that matches the Jira Align sprint (plus buffer days). This was inconvenient for teams who used different cadences because Azure DevOps sprints changed when an edit to a different field happened in Jira Align. We updated this logic so that the existing Azure DevOps sprint won’t change if it already matches a Jira Align sprint (plus buffer days).
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-3717||Capacity Planning Report: Unable to access the report for a particular team||10.103.1|
|JIRAALIGN-2707||Team Room: Progress Bar on Stories without Tasks||10.103.1|
|JIRAALIGN-2341||User Story shouldn't retain the old PI after assigned to the new parent that doesn't have the PI set||10.103.1|
|JIRAALIGN-3581||Central pane (Work Spend) sorting order on Portfolio Room is different in Financials, Execution and Resources||10.103.1|
|JIRAALIGN-3732||Backlog view: Columns Shown dialog lists Developmental Step instead of Process Step for Features||10.103.1|
|JIRAALIGN-3727||Reports: Funding Plan report does not group by solution level programs||10.103.1|
|JIRAALIGN-3694||Epic - Process Steps is blank when changed Primary program||10.103.1|
|JIRAALIGN-2968||Using Ampersands when adding Exit Criteria to Process Steps doesn't work.||10.103.1|
|JIRAALIGN-1867||Connector Jira - The rich text doesn't support <colgroup> HTML tag||10.103.1|
|JIRAALIGN-510||Program Board: User is not informed that Target Completion of Story is after Dependency Target Completion||10.103.1|
|JIRAALIGN-3722||Multiple Teams and large Description in Program Board Quick View displaying||10.103.1|
|JIRAALIGN-3616||Selecting Members Tab in a Portfolio Team errors if only the Portfolio Teams toggle is enabled||10.103.1|
|JIRAALIGN-3546||Change Activity log not honoring 'Records Displayed Per Screen' preference||10.103.1|
|JIRAALIGN-3073||Backlog Ranking: JA Feature ranking is not completely pushed to Jira||10.103.1|
|JIRAALIGN-3553||Push Rank of Features from Jira Align with multiple connectors to Jira does not work||10.103.1|
|JIRAALIGN-3768||The drop down list from Recycle Bin/Cancel Objects pages does not reflect the Platform Terminology naming customisation||10.103.1|
|JIRAALIGN-3565||Defects: Using magnifying glass allows the assignment of a Story that belongs to a different Program||10.103.1|
|JIRAALIGN-3662||API: 'Key Results' calls have a "Nullable object must have a value" error||10.103.1|
|JIRAALIGN-3585||API 2.0: Updates to Epics are not allowed if the Theme is inactive/deleted, nor if the owner is inactive||10.103.1|
|JIRAALIGN-1848||Estimation: Values are rounded in different ways||10.103.1|
|JIRAALIGN-2294||Estimation: Work item with Business Value/Time Value/RR/OE Value/Job Size set to 0 doesn't appear in the Column view||10.103.1|
|JIRAALIGN-2042||Features: WSJF page shows the same feature while operating in different tabs with different features||10.103.1|
|JIRAALIGN-2071||Copy-pasting a text that includes a comma on epic tags results in 2 tags||10.103.1|
|JIRAALIGN-2773||Unable to change Owner field for some of the Release Vehicles||10.103.1|
|JIRAALIGN-3726||Kanban board gets an internal error||10.103.1|
|JIRAALIGN-3720||Historical data for Health in Theme Group in Jira Align is not Updated||10.103.1|
|JIRAALIGN-3701||While updating an existing dependency we are able to select a solution for the "Depends On" drop-down||10.103.1|
|JIRAALIGN-1348||Modifying Fix Version Dates (begin & end) don't sync correctly via the connector [Missing End Date Modification]||10.103.1|
|JIRAALIGN-818||JIRA Connector: Connector shouldn't remove the ship date from release vehicle after it was pushed to Jira||10.103.1|
|JIRAALIGN-2306||Jira Connector: Jira Management Filtering Disappears When Clicking On Team and Navigating To the Sprint Tab||10.103.1|
|JIRAALIGN-3037||Jira Connector: Release Vehicle/Fix Version name is only syncing from Jira to Jira Align||10.103.1|
|JIRAALIGN-3099||Jira Connector: Ship Date (JA) --> Release Date (JS) do NOT sync from Jira Align to Jira||10.103.1|
|JIRAALIGN-3525||Jira Connector: Release Vehicle Launched State only syncs from Jira to JA||10.103.1|
|JIRAALIGN-915||Bi directional Work Item (Issue Sync) - Tag and Label sync is inconsistent||10.103.1|
|JIRAALIGN-3667||Adding an empty state mapping and then editing it causes state mapping duplicity||10.103.1|
|JIRAALIGN-3664||Release Vehicles permission Add/Delete/Save toggle is OFF but parent permission "Release Vehicles" is ON; can change External Reference Link & Consolidate Release Vehicles||10.103.1|
|JIRAALIGN-3358||Team Room : Story progress bar pop-up shows wrong progress when task effort hours is '0'||10.103.1|
|JIRAALIGN-3736||MassUpdate not displaying items when the Release/PI is set to Unassigned Backlog||10.103.1|
|JIRAALIGN-3522||If HTML format or space is contained, Description is updated, even no change is made||10.103.1|
|JIRAALIGN-3444||Milestones: lastUpdatedDate property is not updated when Health is changed via UI||10.103.1|
|JIRAALIGN-3160||User Tagging in all comment areas changes "ë" char into "ë"||10.103.1|
|JIRAALIGN-3731||Platform Terminology: emails sent by the Responsibility Assignment Matrix for Capabilities are using the terminology of Epics||10.103.1|
|JIRAALIGN-3619||Objectives: Reference attribute removed from Audit Log after 10.98 release||10.103.2|