Release Notes for 10.97.X

The Atlassian Jira Align team is pleased to announce the release of Jira Align v.10.97.

• Enhancements and Features
• Defect Fixes

Enhancements and Features

These features will be released to environments on the continuous release track on June 18, 2021, in version 10.97.0. The features will then be released to environments on the bundled release track on July 2, 2021, in version 10.97.2:

Important: API 2.0 changes (previously mentioned in 10.96 release notes)

In an effort to match property names with the Align UI and standardize property naming conventions, we changed the properties listed below. We understand that these changes impact existing integrations, but believe the changes will significantly improve the usability of the API. We’re delivering all necessary changes to an object in a single release (e.g. all changes to the Epic API will be in this release), and we expect to complete the work for all objects within the next two to three feature releases.

Epics

• isCanceled was added
• isSplit was added
• parentSplitId was added
• spendToDate was added
• estimateAtCompletion was added
• startDate changed to startInitiationDate
• estimateDate changed to portfolioAskDate
• targetDate changed to targetCompletionDate
• driver changed to strategicDriver
• budgetTw changed to teamWeekBudget
• complexity changed to kanoComplexity
• certainty changed to kanoCertainty
• kano changed to kanoCategory
• opExE changed to externalOpEx
• capExE changed to externalCapEx
• capEx changed to totalCapEx
• opEx changed to totalOpEx
• irate changed to discountRate
• initialInv changed to initialInvestment
• fyears changed to forecastYears
• f1 changed to yearlyCashFlow1
• methodType changed to planningMode
• bimpact changed to businessImpact
• appetit changed to riskAppetite
• fimpact changed to failureImpact
• fprob changed to failureProbability
• abilityExec changed to abilityToExec
• leanUx changed to leanUxCanvas
• rank was removed
• globalRank was removed
• backlogType was removed
• dropCount was removed
• lastModifiedDate was removed

Capabilities

• kano changed to kanoCategory
• leanUx changed to leanUxCanvas
• startDate changed to startInitiationDate
• estimateDate changed to portfolioAskDate
• targetDate changed to targetCompletionDate
• backlogType was removed

Iterations

• lastUpdatedDate was added
• sprintScheduleId changed to schedule
• stateId changed to state
• velocity changed to overrideVelocity
• typeId changed to type
• hardeningHours changed to regressionHours
• owner was removed
• ownerUid was removed
• weather was removed
• isTerminated was removed
• used was removed
• goalState was removed
• teamCommit was removed
• notes was removed
• capacityThreshold was removed
• stateWasAutoChanged was removed

Important: API 2.0 changes planned in 10.98.0

To allow for more time to prepare for property changes, below are the planned changes for release version 10.98.0.

Features

• isSplit was added
• spendToDate was added
• estimateAtCompletion was added
• blocked changed to isBlocked
• ticket changed to associatedTicket
• countryIds changed to affectedCountryIds
• parentSplit changed to parentSplitId
• startDate changed to startInitiationDate
• estimateDate changed to portfolioAskDate
• targetDate changed to targetCompletionDate
• opExE changed to externalOpEx
• capExE changed to externalCapEx
• capEx changed to totalCapEx
• opEx changed to totalOpEx
• irate changed to discountRate
• initialInv changed to initialInvestment
• fyears changed to forecastYears
• bimpact changed to businessImpact
• appetit changed to riskAppetite
• fimpact changed to failureImpact
• fprob changed to failureProbability
• abilityExec changed to abilityToExec
• leanUx changed to leanUxCanvas
• createdDate changed to createDate
• categoryId changed to category
• driverId changed to businessDriver
• functionalAreaId changed to functionalArea
• lastModifiedDate was removed
• iterationId was removed
• split was removed
• featureStory was removed
• firstName was removed
• lastName was removed
• emailAddress was removed
• scenario was removed
• revenue was removed
• development was removed
• roi was removed
• targetRelease was removed
• grade was removed
• impact was removed
• solution was removed
• fileName was removed
• position was removed
• featureName was removed
• useCases was removed
• addRequirements was removed
• dropCount was removed
• rank was removed
• capacityRank was removed
• epicRank was removed
• portfolioRank was removed
• releasePortfolioRank was removed
• releaseRank was removed
• releaseGlobalRank was removed
• valueStreamRank was removed
• valueStreamReleaseRank was removed
• globalRank was removed
• methodType was removed
• pendingApprovalDateEnd was removed
• readyToStartDateEnd was removed
• inProgressDateEnd was removed
• devCompleteDateEnd was removed
• testCompleteDateEnd was removed
• backlogType was removed

Stories

• lastUpdatedDate was added
• typeId changed to type
• automationId changed to automation
• acceptedUserId changed to acceptedBy
• split changed to parentSplitId
• droppedDate was removed
• backlogType was removed
• lastModifiedDate was removed

Tasks

• lastUpdatedDate was added
• lastUpdatedBy was added
• taskTypeId changed to task
• totalHours was added
• lastModifiedDate was removed

Defects

• categoryId changed to category
• areaId changed to functionalArea
• blockedChk changed to isBlocked
• blocked changed to blockedReason
• duplicateOfChk changed to isDuplicate
• reproduce changed to stepsToReproduce
• suite changed to defectSuiteId
• databaseUsed changed to database
• customerIssue changed to isCustomerIssue
• commercialize changed to isCommercialized
• pmReview changed to isPmReviewed
• affectDoc changed to isAffectingDoc
• inProgressDatewas removed
• lastModified was removed
• detectedBy was removed
• detectionDate was removed
• productType was removed
• testCaseId was removed

Jira Connector usability improvements: The Why button

We've made three key improvements to how the Jira Connector works with relation to the Why button:

• Connector performance
  We've made some changes to reduce the number of updates the connector needs to make in order to keep the Why field updated in Jira. We will continue making small changes like this iteratively, as we move closer to an optimal solution to keep this field current between Jira Align and Jira. Since we know there will be some time before we can provide an optimal solution, we have added some functionality to improve the experience on the Jira side.

• Why button now uses a work item's State field instead of Progress
  The goal with this change was to keep the value of understanding how close a parent item is to being done, while reducing the number of updates the connector needs to make in order to keep states up to date. Currently, the connector will continue to only update the Why button information when a feature in Jira Align is updated, while additional changes to improve sync are planned.
  

• Why button contents now include Jira Align IDs
  Because the connector needs a Jira Align feature to be updated in order for the Why button contents to update, we have added Jira Align work item IDs to the contents of the Why button display in Jira. This way, if a work item title changes in Jira Align, you still have a consistent way to search for the work item through its ID. 

Jira Connector usability improvement: Capability parent sync

We now sync the Capability Parent (read-only text field) field with Jira, to provide more top-down visibility when working in Jira. This field functions the same as Feature Parent Name and is available for both Classic and Next-Gen Jira project types.

As part of this effort, we have exposed this field within feature Details panels in Jira Align. See the next enhancement below.

Feature Details panels now display parent lineage

While we were making changes to improve the connector integration experience, we had an opportunity to improve the Details panel experience for features. Now, you can see the entire parent lineage in the Contained In field when viewing a feature. This provides a direct link to each parent level in your work item hierarchy, up to themes. You no longer have to select Requirement Hierarchy and search within all the items to find direct parents.

Work Tree views pagination

We've improved the performance of Work Tree pages that contain large and complex hierarchies. For all Work Tree views, we added pagination whenever there are more than 50 child work items underneath a parent. Use the View More button to load items in groups of 50, similar to the other pages in Jira Align.

This improvement helped to resolve several customer-reported defects and enhanced average loading speed for many Work Tree configurations by a significant amount.

Invalid filter option removed from Work Tree

To resolve a customer-reported defect, JIRAALIGN-2309, we removed the Text/Tag option from filter settings found in the Extra Configs menu. Note that no functionality has changed, as this option did not function correctly. 

Changes to session timeout warning

We've improved your experience when a session with Jira Align is about to expire. As reported in JIRAALIGN-1637, many users were not seeing the pop-up message at the top of the screen that warned a logout was about to happen. Users who were logged out were not returned to the log in screen and could continue making invalid edits in an open item's Details panel. We've changed the format of the warning, which will not allow page edits to take place when a session ends. 

Updates to Activity Log to display API actions

To resolve JIRAALIGN-2883, we've changed the icon displayed inside of Activity Logs when a change is made through our APIs. User-made changes will continue to display a clipboard icon, which API-issued changes will display a gear icon on the left side of the entry's row. 

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.

Note that versions 10.97.1 and 10.97.3 were not deployed, due to no changes within the release.