Release Notes for 10.74

• Release Notes Updates
• Enhancements and Features
• Defect Fixes

A change to our release cadence in July

Due to a US holiday, the 10.74 production environment release has been moved from July 4, 2020 to July 18, 2020. You can review our updated release calendar here.

Subscribe to real-time release note publication notifications

With the Jira Align 10.74 release, we will no longer be sending our release announcement email. We recently enhanced the Help Center to allow those with accounts to sign up for release notes publication notifications. So, no longer will you have to wait until the beginning of the week after a release to review the details of new and enhanced features, performance improvements, and defect fixes. Now, you'll receive a notification the moment release notes are published on the Friday prior to a release.

Shareable links

Shareable links are here! One of your most-requested enhancements, we’ve added functionality to include top-level filter settings in the URL of Jira Align pages. Now, you can navigate throughout the platform and share your filtered view with your team! (Of course, all views will still be limited by user permissions, so one can’t get too extreme). Simply copy-paste your URL to share your filtered page.

Currently, this functionality supports filters set in the Configuration bar. For example, if you specify one program and two program increments, your URL will look similar to:
https://yourinstance.agilecraft.com/EpicGrid?FirstTime=True&Programs=30&Releases=68,69 

Soon, we’ll extend this functionality to grid page filters, so stay tuned.

Feature label added to Story Map cards

Story maps are a great way to turn customer journeys into a backlog, plan releases, or simply organize stories across two dimensions. In this release, we’re adding a feature label to the story cards. This will help users easily identify which stories have already been parented to a feature and which need to be.

Microsoft Azure DevOps connector enhancements

• Previously, the Azure DevOps (ADO) connector required that a single ADO project area path maps to a Jira Align program. Now, multiple ADO project area paths can map to one Jira Align program. This allows you to quickly integrate ADO teams and map them to an optimal teaming hierarchy in Jira Align, without having to restructure ADO.

• To support the change above, a new Azure DevOps Area Path attribute was added to work items. This will display on items in programs mapped to area paths in your connector configurations. When syncing items from ADO, this will field will automatically be set. When creating items in Jira Align, this attribute will need to be set in order for the items to sync to ADO. Once set, this field becomes read-only. Items will need to be moved in ADO in order for the area path to change.

• The ADO connector has three sync timers, each controlling the cadence at which work items, teams and sprints, or recycle bins sync. These settings were moved out of a back-end configuration file and into the configuration settings so that you can adjust the sync cadences to meet your needs. In addition, we added timestamps below each setting so that you can easily see when a timer last ran or if it is currently running.

• Bidirectional syncing of acceptance criteria is now supported! If you choose to sync acceptance criteria, you’ll be limited to a single acceptance criteria text field in Jira Align since the default ADO acceptance criteria is a text field. If you already have multiple acceptance criteria in Jira Align, the connector will automatically merge them into a single, formatted text field.

Jira connector enhancements

On the Jira connector sprint mapping page, a new indicator was added to highlight sprints that have been deleted in Jira or that the connector longer has access to. In addition, we added an action to delete the Jira sprint from the mapping (previously you could ignore the sprint in the mapping but not delete it). Note, this action will not delete Jira sprints or Jira Align sprints, it simply deletes it from the mapping page.

Objective and Key Results APIs

We've added read APIs for the Objective and Key Results objects. In the following releases, we'll be adding support for the create and update actions.

Defect Fixes