Note: Due to a deployment issue with previously reported features, 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 section below for details:
Previously reported features and defect fixes
Changes to the Jira connector were previously detailed in these notes, but due to deployment issues, were not released to environments in version 10.115.0. These changes will ship in the near future and will be included in an upcoming Release Notes article:
- Improved setting and custom field names for Jira connector settings
- Sync of Sprint goal fields when updating sprints, instead of only syncing during creation
The Atlassian Jira Align team is pleased to announce Jira Align v.10.115.
Enhancements and Features
These features for 10.115 were released to environments on the continuous release track on December 16, 2022, in version 10.115.0. The features will then be released to environments on the bundled release track on January 6, 2023, in version 10.115.3:
In version 10.118.0, we’ll be removing the remaining pages that make up the Collaborate menu inside of Jira Align. We’ll also remove access to the Rational Team Concert (RTC) and Trello connectors.
After reviewing recent usage data, it became clear that this functionality was not providing significant value. By removing these features 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.
Pages inside the Collaborate section of the left-side navigation menu allow you to create and document internal communications, publish blogs and newsletters to your Jira Align users, and host forums. In version 10.112.0, we removed the first page from this section, Awards / Shoutouts.
As part of Atlassian, we believe you can gain more value using purpose-built products, such as Confluence, to create and store internal communications.
Pages that will be removed include:
System role permission toggles related to these pages will also be removed from Admin > Roles.
- *The Communities of Practice (CoP) page and the ability to create a new CoP will be removed. However, 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 will no longer provide 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 after removal, 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.
If you have used Collaborate functionality in the past and would like to make a record of your entries, please visit these pages prior to version 10.118.0 to capture your data. You can use screenshots and Save options from your browser to make a record of past blogs, newsletters, and forum entries. For images, you can right-click on an entry and select Save Image As to download a copy.
Trello connector and Power-Up
The Trello connector provides the ability to sync cards on a Trello board to Jira Align defects, stories, and features on a custom Kanban board. Inside Trello, the Jira Align Power-Up provided the ability to designate a card as a defect, story, or feature, and provided access to Cumulative Flow Diagrams and Burnup Charts.
If you’ve used the Trello connector in the past, we recommend moving your Kanban teams from Trello to Jira, where they can continue to sync Jira data to Jira Align. See more details in our Jira - Jira Align Kanban Setup article on Atlassian Community.
Items that will be removed include:
- Trello Connector Setup settings in Jira Align at Admin > Connectors > Trello Settings.
- The Jira Align menu and charts displayed at the top of a Trello board when the Jira Align Power-Up is enabled.
- The Jira Align option inside Trello’s Power-Ups menu.
After the connector is removed, your cards in Trello and the synced work items in Jira Align will remain available for archival purposes. Changes made in either system will no longer sync.
Rational Team Concert connector
The Rational Team Concert (RTC) connector provided the ability to sync stories and tasks between RTC and Jira Align. We have not offered this connector for new Jira Align instances since joining Atlassian. Removing this legacy connector from our codebase will allow us to streamline our testing practices.
After the connector is removed, your tasks and stories in RTC and the synced work items in Jira Align will remain available for archival purposes. Changes made in either system will no longer sync.
Objectives Tree: Progress bars per work item type
We’ve added some new column options to the Objectives Tree (new experience):
- Story points accepted: story points of completed stories and their percentage
- Stories accepted: the percentage of completed stories that are assigned to the objective
- Feature progress: the percentage of completed features that are assigned to the objective
- Capability progress: the percentage of completed capabilities that are assigned to the objective
- Epic progress - the percentage of completed epics that are assigned to the objective
If no work items are assigned or mapped to the objective, a gray progress bar will display. Pointing to the empty progress bar will display a ”No work items assigned” tooltip.
Try out the new columns by turning them on in the Columns shown dropdown
Objectives Tree: Sorting changes
When sorting by the Summary, Team, Owner, or Target Completion column on the Objectives Tree (new experience), the secondary ordering of objectives (between an objective summary, a team, an owner, or a target completion date) now is ordered by objective ID in descending order.
When sorting by the Status column, ordering is now first by the Objective summary according to the column sorting, and then by the Objective ID in descending order between objective summaries.
The sorting by Objective ID in descending order also applies to the goal and child objective cards in the hierarchy view.
API 2.0: Support for the DELETE method
We’ve added API 2.0 support for the DELETE method for the following items:
Value streams (process flows)
- Release Vehicles
Estimation system corrections for mismatched features
As part of resolving JIRAALIGN-2288, we’ve updated which estimation system is displayed on a feature when there may be a conflict between the associated program increment and portfolio. Jira Align will use the relationship between the feature’s primary program and portfolio to determine what estimation system is shown.
To understand this change, consider the following scenario:
- Portfolio A uses a t-shirt size estimation system.
- Program 1 is a child of the portfolio.
- Portfolio B uses a team weeks estimation system.
- Program 2 is a child of the portfolio.
- Program Increment Winter 2022 is created and associated with Portfolio B.
- Feature X is created:
- Program 2 is set as the primary program
- Winter 2022 is set as the PI
- One change is made — PI Winter 2022 is edited, moving the portfolio assignment from B to A.
- This results in a portfolio mismatch: The feature is associated with Portfolio B through its program, but is also associated with Portfolio A through its PI.
Previously with this configuration, viewing Feature X’s Details panel would display T-shirt for the estimation field, as the relationship between the PI and Portfolio A was used to locate the estimation system.
Now, viewing Feature X’s Details panel will display Team Weeks for the estimation field, as the relationship between Program 2 and Portfolio B is used to locate the estimation system.
This change for features is now consistent with existing behavior for epics and capabilities. When viewing a grid page of work items that contain these mismatches, you can display multiple estimate fields to see how estimates line up within the same system. Values are converted between each estimation system according to your selections in the Estimation Conversions settings menu.
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-1266||Jira Align Connector does not allow duplicate Jira Board IDs (and Boards are in different Jira environments)||10.115.0|
|JIRAALIGN-2288||The feature estimation method is incorrectly changing||10.115.0|
|JIRAALIGN-2934||Value Engineering Report: Currency Field data does not have a comma||10.115.0|
|JIRAALIGN-2976||Jira Connector updating description of stories in Jira Software||10.115.0|
|JIRAALIGN-3668||Objective Grid Tier Filter disappears after first page||10.115.0|
|JIRAALIGN-3918||Create Objectives link does not work in an empty objectives view.||10.115.0|
|JIRAALIGN-3935||Setting custom team field mapping with space causes connector sync failure||10.115.0|
|JIRAALIGN-4026||Unable to Filter Objectives by Owner with Special Character on Name||10.115.0|
|JIRAALIGN-4263||Editing Key Results in Objectives does not show the save button.||10.115.0|
|JIRAALIGN-4401||When using Point Estimation, Features get assigned 0 points by default if no points are selected||10.115.0|
|JIRAALIGN-4405||Program Board: "Committed by" and "Needed By" Column displays no values for program dependencies||10.115.0|
|JIRAALIGN-4418||Setting multiple Release Vehicles in the filters shows duplicate feature rows in the roadmap.||10.115.0|
|JIRAALIGN-4460||Jira Connector service wrongly identifies as Not Cloud resulting in the wrong user mapping logic being applied||10.115.0|
|JIRAALIGN-4461||Feature Map page - Pressing "Save & Close" after creating Feature don't pin the Features in the Map||10.115.0|
|JIRAALIGN-4475||PI - Add/Save toggle doesn't allow to Add/Save||10.115.0|
|JIRAALIGN-4480||Roadmap: Epic State filter doesn't work||10.115.0|
|JIRAALIGN-4495||Status Report: sort for the columns Rank and Budget is not working as expected||10.115.0|
|JIRAALIGN-4502||When removing endSprintID field of a Feature through API startSprintID is removed as well||10.115.0|
|JIRAALIGN-4503||When updating endSprintID field of a Feature through API nothing is being logged in Audit Log of the Feature||10.115.0|
|JIRAALIGN-4521||Dependency - users are able to create it, even Needed by Date is required on dependencies||10.115.0|
|JIRAALIGN-4525||Roadmap - Adding notes on child nested Work items doesn't show unless you refresh the page||10.115.0|
|JIRAALIGN-4553||Roadmap release view: Clicking on a capability opens the Epic grid||10.115.0|
|JIRAALIGN-4555||Roadmap (Release Vehicle view): Highlighted objects panel detail opens in a new tab||10.115.0|
|JIRAALIGN-4578||Release (Program Increment): Character length field validation limits the number of Programs that can be added to the Release||10.115.0|
|JIRAALIGN-4588||Features: Record About Parent Epic instead of Capability is shown in Audit Log after Feature creation||10.115.0|
|JIRAALIGN-4632||Objectives Tree - "At Risk" filter not working with additional pages of work items||10.115.0|
|JIRAALIGN-4461||Feature Map page - Pressing "Save & Close" after creating Feature doesn't pin the Features in the Map||10.115.3|
|JIRAALIGN-4577||Capabilities Grid: Whoops error due to malformed SQL query||10.115.3|
|JIRAALIGN-4586||Roadmap: No filter in the Configuration bar allows users to view all themes ignoring the team membership||10.115.3|
|JIRAALIGN-4599||Points on Capacity Planning report are divided for a Sprint||10.115.3|
|JIRAALIGN-4613||Changes to custom field sets in Epics Benefits tab record incorrect field name in Audit log||10.115.3|