Jira Align EI Enhancements and Features Version 10.86


Vector.png

The old navigation will be removed from Jira Align in early 2024.
Learn more about the upcoming changes


Jira Align's Enterprise Insights (EI) was updated and deployed to test instances running version 10.86 on January 12, 2021, and will be deployed to production instances on January 16, 2021. The following enhancements were made:

Updated: 10.86.1 hotfix

  • ETL was updated to handle an unexpected NULL data condition in the Roadmap Health Source Query. This update was promoted to test instances on January 13, 2021 and will be included in the January 16 production release. This change had no impact on schema or data content.

  • DW was updated to correct time tracking views for Billing Code in the [time] schema which restricted results to only the Release Vehicle type Billing Codes. The views are updated to include Epic and Stand-Alone values. The affected views were [MAP Billing Code to Cost Center], [MAP Billing Code to Program], [MAP Billing Code to Team] and [MAP Billing Code to Work Code]. This change has no impact on schema, but will result in new rows in the affected tables if applicable. This update was promoted to test instances on January 13, 2021 and will be included in the January 16 production release. This change had no impact on schema or data content.

Release highlights

  • Added Roadmap Health information for capabilities and epics.

  • Added objective external references.

  • Added Team Foreign Key to value streams (process flows).

  • Updated source query to include team members with no team role assignment in Team Member and Sprint Team Member tables.

  • ETL execution management improvements to handling and recovery of processing failures.

New tables

View Name

Description

Capability Roadmap Health

Roadmap Health Status History. This table contains the health status label from the roadmap table. It is a history table and includes all previous values for the capability with an updated timestamp to indicate the time of the change. The current value can be identified by a Yes value in the [Current Value Flag] column.

  • [Capability Roadmap Health ID] INT NOT NULL PRIMARY KEY
  • [Current Value Flag] NVARCHAR(3) NOT NULL
  • [Date Updated] DATETIME NULL
  • [FK Capability ID] INT NOT NULL
  • [FK User Updated By ID] INT NOT NULL
  • [Health Label] NVARCHAR(50) NULL

Epic Roadmap Health

Roadmap Health Status History. This table contains the health status label from the roadmap table. It is a history table and includes all previous values for the epic with an updated timestamp to indicate the time of the change. The current value can be identified by a Yes value in the [Current Value Flag] column.

  • [Current Value Flag] NVARCHAR(3) NOT NULL
  • [Date Updated] DATETIME NULL
  • [Epic Roadmap Health ID] INT NOT NULL PRIMARY KEY
  • [FK Epic ID] INT NOT NULL
  • [FK User Updated By ID] INT NOT NULL
  • [Health Label] NVARCHAR(50) NULL

Updated tables

View Name

Description

External Reference

Objective Foreign Key added to the External Reference table. The [Object Type] column will also describe the item as an objective.

  • [FK Objective ID] INT NOT NULL

Team Member

Previously, team members without a team role assignment were excluded from export to Enterprise Insights. We modified the source to include these team members. Team members without a role assignment will have a Team Role Type of Business Stakeholder and a Team Role Name of No Role Assigned.

Sprint Team Member

Previously, sprint team members without a team role assignment were excluded from export to Enterprise Insights. We modified the source query to include these team members. Sprint team members without a role assignment will have a Sprint Team Role Type of Business Stakeholder and a Sprint Team Role Name of No Role Assigned

Value Stream

A team is automatically created when a value stream (also called a process flow) is created. The Foreign Key to this Team ID has been added to the Value Stream table. Note that in Jira Align, the value stream (process flow) team type will be labeled a Solution Team.

  • [FK Team ID] INT NULL
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.