Ongoing health status field in Jira Align Features grid

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Ongoing health "Status" can't be edited for non-standalone features.

Environment

Jira Align

Diagnosis

Status can be set by clicking the Status cell of an epic to assign a status of On Track, Some Risk, or High Risk.

Status: Ongoing health of the epic as defined by the user. Click the Status cell of an epic to assign a status of On Track, Some Risk, or High Risk. This is a subjective evaluation based on the opinion of the epic owner that is designed to supplement the metrics-based data generated by Jira Align. The past six status evaluations entered by users are displayed in the cell as small cards.

Standalone Feature = That has no parent Epic or Capability

Non-Standalone Feature = That has parent Epic or Capability

Cause

The stated ongoing health “status” field is specially used/designed for the Status Report at Enterprise Level. That report covers work items that roll up to the Portfolio, so the Jira Epic (Non-standalone Feature) is not included in this level of report or view. The main reason for that is Jira Epics (Non-standalone Feature) should be managed at Program Level (I.e Program Board).

How to Replicate

  1. Program > Feature Epics and select Portfolio in the filter.

  2. Enable the "Parent Object" and "Status" toggle under Columns to show

  3. Verify N/A in the status cell for the Features that have parent Epic or Capability

(Auto-migrated image: description temporarily unavailable)

Solution

  • Standalone Features/Jira Epic” are exceptions; the reason is that they do not have any parent Epic/Capability; hence, they are being reflected in the Enterprise Level Status Reports for visibility and tracking purposes.

  • Besides, Jira Epic (Non-standalone Feature), which has a parent Epic or Capability, does not have the Status field in the Feature grid/view, and it is not visible in the enterprise-level status report. Only its parent epic is visible in the status report.

  • Overall that is an expected behaviour.

Updated on April 14, 2025

Still need help?

The Atlassian Community is here for you.