Alternative Jira Health Checks After the Jet by Jira Align Retirement

[#1]

As communicated in the Jira Align release notes for the last quarter, the JET App was designated with end-of-support (EOS) status on September 17, 2025. We are planning to remove access to the app sometime before December 31, 2025. The removal is in support of Atlassian’s EOS plan for marketplace apps built with Connect.

Jet was a tool for examining your team's use of Jira to ensure readiness to scale agile practices. Running the JET analysis helped teams and programs prepare for scaled agile by highlighting the areas that need remediation to provide consistent reporting across teams.

Jet's seven health checks, remedial actions and suggested future analysis methods:

Check #1: Stories should be linked to epics.

Stories with parent epics provide an accurate representation of how your work rolls up into your strategic themes.

Remedial Action

Make sure you've linked an epic in your story.

Future Analysis Method

JQL Example: issuetype = Story AND "Epic Link" is EMPTY

API Example: GET /rest/api/3/search/jql?jql=issuetype%3DStory%20and%20parent%20is%20EMPTY to check for the presence of parent epics.

Check #2: Stories should have estimated story points.

Stories that have story points provide an accurate representation of your progress.

Remedial Action

Add estimates to your story points fields in your stories.

Future Analysis Method

JQL Example: issuetype = Story AND (Story Points is EMPTY or Story Points = 0)

API Example: GET /rest/api/3/search/jql?jql=issuetype%20%3D%20Story%20AND%20%28"Story%20Points%5BNumber%5D"%20is%20EMPTY%20or%20"Story%20Points%5BNumber%5D"%3D0%29 to check for the presence of story points.

Check #3: Epics should have an assigned fix version.

Epics should have fix versions to dictate what release the epics will be shipped on. Releases are tied to a project in Jira.

Remedial Action

Assign a fix version in the "Version" item under a project's settings.

Future Analysis Method

JQL Example: issuetype = Epic AND fixVersion is EMPTY

API Example: GET /rest/api/3/search/jql?jql=issuetype%20%3D%20Epic%20AND%20fixVersion%20is%20EMPTY to check for the presence of versions.

Check #4: There should only be one project assigned to a Jira board.

Multiple projects linked to a single board can make it difficult to measure team-level progress. That board can represent multiple teams and have sprints with overlapping dates.

Remedial Action

Ensure only one project is tied to a board by navigating to Board Settings, selecting Edit Filter Permissions, and removing all but one project. You may also fail this check if there are no projects tied to your board.

Future Analysis Method

Visual Example: Board settings → General → Permissions: Ensure the Filter Permissions only includes a single project = XYZ condition.

API Example:

• GET /rest/agile/1.0/board

• GET /rest/agile/1.0/board/{boardId}/configuration to check each board’s associated projects.

Check #5: Mark custom fields as optional, not required.

Custom field configuration can affect your ability to integrate with Jira Align, a Scaled Agile tool in the Atlassian suite. If you are only syncing from Jira to Jira Align and you leave any fields as required, they will not be synced. If bi-directionally syncing between Jira Align and Jira, your issue type will fail to sync.

Remedial Action

Please mark any fields other than Description, Reporter and Summary from your issue types custom fields as optional.

Future Analysis Method

Visual Example: Navigate to Jira Settings → Issues → Field Configurations. Ensure only the default fields (Description, Reporter, Summary) are required.

API Example: GET /rest/api/3/fieldconfiguration to inventory field requirement.

Check #6: A single sprint should only be tied to one board.

Because one board represents one team, if you have a sprint on multiple boards, it can make be difficult to measure team-level progress.

Remedial Action

Edit the Filter Query to ensure only a single team's sprints are tied to a board.

Future Analysis Method

API Example: GET /rest/agile/1.0/board/{id}/sprint and build a mapping of sprint IDs → board IDs.

Check #7: Sprints on a board should not have overlapping dates.

Sprints represent a (usually 2-week) planning and execution time slot for a single team. Only one sprint should be active at a time.

Remedial Action

Make sure the start and end dates for your sprints don't overlap.

Future Analysis Method

Visual Example: From the board’s backlog, expand Sprints and check date ranges.

API Example:

• GET /rest/agile/1.0/board

• GET /rest/agile/1.0/board/{id}/sprint comparing startDate and endDate for overlap.