The Atlassian Jira Align team is pleased to announce Jira Align v.10.118. Please note that the 10.118.0 feature release was not deployed, as our developers worked to ensure the release met our standards for quality. As a result, the feature release for 10.118 is version 10.118.1.
Enhancements and Features
These features for 10.118 were released to environments on the continuous release track on March 17, 2023, in version 10.118.1. The features will then be released to environments on the bundled release track on March 24, 2023, in version 10.118.2:
Changes coming next week to support a new Jira Software epic field
Later next week, Jira Software Cloud will begin rolling out changes to epic fields in company-managed projects.
If your Jira Align instance is currently connected to one or more Jira Software Cloud projects, you will see the following changes as of Tuesday, March 21:
- On the Admin > Jira Settings > Jira Setup connector settings page, the Feature name custom field custom field mapping will be renamed to Jira epic name custom field and will be made optional. Existing mappings will not be removed.
- Inside of Details panels for Jira Align features, the Summary field will be renamed to Jira Epic Name and will be made optional.
- The Jira connector will begin syncing the Summary field of Jira Software epics with the Title field of Jira Align features. The connector will also begin syncing the Epic Name field of Jira Software epics with the Jira Epic Name field of Jira Align features.
See our announcement, Upcoming changes to support a new Jira Software epic field, for full details of the change and steps you can take to prepare.
Removal of Collaborate pages, Trello connector, and Rational connector
As previously announced, we've removed the remaining pages that make up the Collaborate menu inside of Jira Align. We've also removed access to the Trello and Rational Team Concert (RTC) connectors. Pages removed include:
- Communities of Practice*
- Trello connector settings
- Jira Align Power-Up inside of Trello (removed March 10, 2023)
- Rational connector settings
If you attempt to visit these locations through a previously-saved link, bookmark, or Favorites entry in Jira Align’s navigation, you’ll be redirected to a new page that informs you the functionality has been removed. Select the Learn more link from the page to see more info about recently removed functionality, as well as instructions on how to clear old entries from Favorites.
- *The Communities of Practice (CoP) page and the ability to create a new CoP were removed. You may still create a new team with a Type field set to Community of Practice. For a short time after removal, you may associate these types of teams with a previously-created CoP. We recommend leaving this field blank in those situations, as the field no longer provides any functionality. Existing CoP-type teams that are associated with a CoP will show the association. This can be removed manually by editing the team’s Details panel. Sometime later in 2023, these associations and fields will be removed from Jira Align.
- For a short time, you may still be able to access individual blog posts through their direct URLs. We recommend working with your teams to ensure any links or bookmarks to specific blog posts are removed from your internal websites, intranet, and wikis.
API 2.0: Consistent method support, consistent object coverage, and complete property coverage
We’re kicking off an effort to ensure consistency in our API coverage. This means making sure that all objects have consistent method (GET, POST, PUT/PATCH, DELETE, etc.) support, consistent coverage (support for audit logs, acceptance criteria, links, etc.), and that all object properties (epic field financial fields, release sync sprints, etc.) are available.
This release includes:
- GET, POST, PUT, and PATCH support for capability acceptance criteria
- POST, PUT, and PATCH support for capability links
- GET, POST, and PUT support for epic acceptance criteria
- POST, PUT, and PATCH support for epic links
- PATCH support for releases
- PUT and PATCH support for value streams
- GET, POST, PUT, PATCH, and DELETE support for Jira connector product mappings
- Copy endpoints for capabilities and features
- Audit log endpoints for value streams, products, customers, and cities
Upcoming removal of legacy reports
In version 10.121.0, we’ll be removing five legacy reports from Jira Align:
- Build Status By Sprint
- Escalation Report (not accessible)
- Enhancement by Owner (not accessible)
- Enhancement by Age (not accessible)
See our announcement, Upcoming removal of legacy reports, for full details of these planned removals.
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.
|Splitting a Feature does not replicate the ADO area path in the newly created Feature AND creates orphaned stories in ADO
|Capture does not work for Process Flow (Value Stream) Cycle Time
|When importing Features target sprints do not update if no target sprints were selected before
|Opening a Folio times out due to query constraints
|When updating a custom field via API, only 250 characters are accepted.
|"Fast Edit" feature loads very slowly
|Forecast Page is Not Loading
|In Epic Backlog with Portfolio selected in tier1, when not all of the Epics are loaded, using 'Move to Bottom' assigns rank 10000 and leads to inconsistent results
|Character limit in the Initial Metric field for Success Criteria
|Roadmap- Unplanned work does not sort according to backlog rank
|Accept and Unblock buttons on Dependency Slideout are only partially clickable
|Modifying Capacity in the Forecast page does not log work item changes in Audit Log
|Features/Epics may be showing twice in the Program feature backlog
|Hide time tracking report toggles for sites without a time tracking license
|Forecast Report Not Honoring Configuration Selection
|Renaming a Theme allows for duplicate names
|Feature: Sprint Start and End date show inconsistencies when PI is changed
|The Select list for Ideation Group's Admins and Internal Contributors fields shows all the pre-selected names as well, instead of just showing only the name matching the search criteria
|Disabling Ideation permission does not prevent access to Ideation
|Features are listed twice in the live Roadmap
|Program Room: Text search function is not filtering properly
|Theme Import: Themes without a valid state can be imported
|ROI Calculator is incorrect
|Capabilities: Inconsistency in role toggles controlling the Links section
|Objective Tree: Incorrect count in Status Card with multiple PIs
|Backlog : Poor performance on re-ranking item, the screen automatically scrolls rapidly
|Deleting a snapshot tied to a goal doesn't fully remove the snapshot from the goal
|Ideas: when creating an Idea via API, FeatureName on table tblEnhancement is not created
|Users Non-Super admin are not able to view/add links related to an objective(Portfolio/Program/Team)
|Organizational Hierarchy report – Program shows under wrong solution when filter with Portfolio on T1
|New Objective Tree: Column Names
|New Program Objective - Can't select a parent objective
|Legacy Objective Tree: Clicking on Key Results results in "Error Retrieving data for modal".
|Cannot edit Key Results against an Objective tree - Goal, just get a spinning wheel.
|New sprint mapping setting not available in Jira V8.10 onwards
|Accessing the KeyResults endpoint via non-super user gets 403 error
|Setting a Story to a PI in a Kanban Team displays the story twice in the Backlog
|Feature Backlog - Kanban Value Stream - Exit Criteria Toggle Unexpected Behavior
|Platform > Security: SAML Provider modal displays certificate from a different provider
|Editing a portfolio tier objective in a portfolio with over 200 projects results in "Project text length exceeded 1000 characters" error.
|Legacy Objectives: Setting 'Target' to a value greater than 2147483647 is not allowed
|The filters in Jira Management are not appearing and the add board button is not working
|Epic permission is not being correctly evaluated/respected