Release notes for 10.116.X


Note: Due to an issue with a previously reported feature, 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:

Removal of Jira connector API endpoints
New API endpoints for managing the Jira connector were previously detailed in these notes. To ensure the functionality meets our quality standards, we have decided to remove the endpoints as part of the upcoming 10.116.2 release. Once we are able to confirm that the functionality meets our requirements, we will reintroduce the endpoints in a future feature release.

The Atlassian Jira Align team is pleased to announce Jira Align v.10.116. Please note that the 10.116.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.116 is version 10.116.1.

Enhancements and Features

These features for 10.116 were released to environments on the continuous release track on January 24, 2023, in version 10.116.1. The features will then be released to environments on the bundled release track on January 27, 2023, in version 10.116.2:

Reminder: Upcoming removal of Time Tracking functionality

As previously announced, the Time Tracking module will no longer be available in Jira Align as of the 10.119.0 release.

The Time Tracking module was accessible through a paid entitlement that has not been offered for purchase for two years. After careful evaluation, we’ve determined the existing module no longer aligns with our vision for the future. If you’re looking for a time-based tracking solution with Jira Align, we recommend checking out our integration with Tempo Timesheets.

Jira connector: Sync feature points to a new Jira field

Previously, when syncing feature points and story points with Jira Software, we required you to use the same Jira field for both. When using the default Story points field in Jira, users were often confused as to what Story points were in reference to when displayed on their Jira epics. Additionally, Jira sprint reports were often incorrect as the Jira epic point values were included.

Now, you can sync feature points and story points to unique Jira fields. From the Admin > Jira Settings > Jira Setup tab, you’ll see two separate custom field options: Story points custom field and Feature points custom field.

RNs_10116_PointSyncFields.png

For your existing connectors, there is nothing you need to do to prepare for the change. The Feature points custom field setting will be prepopulated with the Story points custom field value. When you’re ready, you can configure Jira with a new field and update the connector’s custom field mapping.

Jira connector: New sync direction options for t-shirt size estimates

To provide the same options as other similar settings, we added a Jira to Jira Align sync direction option to the T-shirt custom field setting for features. Find this setting under Admin > Jira Settings > Jira Setup. Going forward, you can choose between two sync directions: Jira to Jira Align or Bidirectional.

If you have an active connector that’s currently configured with the t-shirt field sync direction as Jira Align to Jira, that choice will be retained until a new selection is made. We will not automatically remove that option. Once you change the field’s sync direction to either Bidirectional or Jira to Jira Align, the Jira Align to Jira option be removed.

RNs_10116_TshirtSyncDirection.png

We’re phasing out the Jira Align to Jira option for two primary reasons:

First, we want individual teams to manage work in their team tools of choice, like Jira Software. It’s not a great experience when teams are creating stories and epics in Jira, but then have to log in and update a few specific fields on those same items in Jira Align.

The other reason for this change is to prevent the confusion that can occur when some fields are not syncing in consistent directions. If some fields sync from Jira to Jira Align only, some bidirectionally, and some from Jira Align to Jira only, it's hard for everyone to keep track of the best place to make updates.

Jira connector: Enhanced sync of sprint goals and sprint names

Previously, the Sprint goal and Sprint name fields in Jira Software were only synced to Jira Align on the creation of a sprint. Now, they are also synced when the sprint is updated.

Jira connector: Search and pagination added to the team custom field mapping modal

We’ve added the ability to search within the team custom field mapping dialog, to make it easier to find and manage existing mappings.

We also added pagination to the dialog to address page load issues when hundreds to thousands of teams are mapped.

RNs_10116_TeamMappingDialog.png

Jira connector: Improved setting and custom field names and tooltips

The following Jira connector setting and custom field mapping names and tooltips were updated to better reflect the actual connector behavior.

Settings found at Admin > Jira Settings > Jira Setup

Old setting name New setting name

Permission to Edit Epic Name

Allow [feature] title updates from Jira Align to Jira

Enable Rank Sync

Sync story and [feature] ranks

Enable Feature Sync

Allow [feature] sync from Jira Align to Jira

Enable Story Sync

Allow story sync from Jira Align to Jira

Enable Defect Sync

Allow defect sync from Jira Align to Jira

Enable Task Sync

Allow task sync from Jira Align to Jira

Enable Feature State Sync

Allow [feature] state sync from Jira Align to Jira

Enable Story State Sync

Allow story state sync from Jira Align to Jira

Enable Defect State Sync

Allow defect state sync from Jira Align to Jira

Story Creation Requires Team

Does story creation in Jira require a team assignment?

Epic Creation Requires Team

Does epic creation in Jira require a team assignment?

Issue Creation Allows Reporter & Assignee

Does creating stories in Jira allow both an assignee and reporter assignment?

Team Uses Both Parent & Child

Is your Jira Team field a cascading select list?

Team Multiple Drop-Down Menu

Is your Jira Team field a multiple choice select list?

Allow Jira to Overwrite Data

Allow Jira to overwrite Jira Align if two simultaneous syncs conflict

Allow feature point sync from Jira Align to Jira

Allow [feature] point sync from Jira Align to Jira

Allow features to have multiple Jira projects

Assign [features] to multiple Jira projects in Jira Align

Allow Jira to add users to team if they belong to an issue

Assign Jira users to Jira Align teams when associated with stories and defects

Create Iterations in Jira Align from Jira

Create [sprints] from Jira

Allow Jira Align to assign stories to iterations

Allow Jira Align to assign stories to sprints

Synchronize sprint names from Jira

Sync sprint names from Jira

Allow feature point sync from Jira to Jira Align

Allow [feature] point sync from Jira to Jira Align

Allow Feature, Story and Defect Program Increments to be automatically updated by Jira Fix Version Dates

Update [program increment] dates based on sprint or fix version dates

Allow Releases to sync with Jira Fix Versions

Sync Jira Align [release vehicles] with Jira fix versions

Allow Jira to update the team field for stories

Allow Jira to update the team field for stories

Allow Jira Align to create Jira issue web links

Create web links on Jira issues to Jira Align work items

Initial Iteration Start Date

Start date of sprint import

Rich Text Format

Jira text formatting type

Jira Users' Full Name Format

Jira users' full name format

Default System Role for New User(s)

Default system role for new users

Default Team Role for New Users

Default team role for new users

 

Old custom field name New custom field name

Story to Epic Link

[Feature] custom field on stories

Story Points

Story points custom field

Sprint

Sprint custom field

Accepted Date

Resolution date custom field

Organization

Team custom field

Rank

Story and [feature] backlog rank custom field

Delete Item Status

Deleted item status

MMF

MMF custom field

Issue Priority Default

Default Jira Align story priority

Feature Product

Product custom field

Feature 'Portfolio Ask' date field

[Feature] portfolio ask date custom field

Feature 'Start / Initiation' date field

[Feature] start/initiation date custom field

Feature 'Target Completion' date field

[Feature] target completion date custom field

Sync Jira resolver name on stories

Sync Jira resolver name on stories

History Resolution Label

Jira change log resolution label

Why? Details

Why? details custom field

Default User

Default user

Parent Feature Name

Parent work item custom field on [features]

Program Increment (note: there are 2 fields with this name)

[Program increment] custom field

Capability Parent

[Capability] parent custom field

T-Shirt

T-shirt custom field

Business Owner

Business owner custom field

Work Code

Work code custom field

Acceptance Criteria

Acceptance criteria custom field

 

Work Tree performance improvements

As of this version, we’ve completed incremental work to improve the performance of the Work Tree page, one of the most-used Jira Align features. We’ve refactored the way dials and data render on the Top-Down from Epic, Bottom-Up from Story, and Team views, resulting in up to 80-90% faster load times with large datasets.

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 and fields, etc.) are available.

This release includes:

  • Links in Goal GET calls
  • Links in Capabilities GET calls
  • HEAD method for Risks
  • DELETE method for Teams

Watch our new roadmap presentation

Check out the latest news on new Jira Align features and development efforts we’re working on. Our Q4 2022 Product Roadmap presentation is now available.

Note that you will need to be logged into our Help Center site to be able to access the recording. If you don’t already have a login, select the Sign up link to create a new one. This account is not tied to your Jira Align user credentials.

RNs_10116_SignUp.png

 

Defect Fixes

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.

Key Summary Release Version
JIRAALIGN-4153 Not able to add notes in Key Result of type Score check-in 10.116.1
JIRAALIGN-4414 Backlog: when a feature is updated on the Feature Backlog, it disappears from it until the page is refreshed 10.116.1
JIRAALIGN-4471 Importing Capabilities allows additional programs to contain same program as the primary program breaking API PATCH requests 10.116.1
JIRAALIGN-4477 Snapshots disappear from list when modifying a Goal in the new UI 10.116.1
JIRAALIGN-4568 Custom Teams: Team list is no longer alphabetical after v10.113.2 release 10.116.1
JIRAALIGN-4579 Import: Users Excel Import may cause a silent error if the file format is incorrect 10.116.1
JIRAALIGN-4629 Possible to modify Key Results in Portfolio Objectives New Experience with Add/Save permission disabled 10.116.1
JIRAALIGN-4634 Objective Tree grid inconsistency 10.116.1
Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.