Problem Statement:
Following the July 2026 native integration update between Jira and Atlas, the automatic synchronization of project statuses to Jira custom fields (e.g., atlasProjectStatus) was removed to support the new one-to-many (1:N) linking model. As a result, customers can no longer use JQL to filter Jira issues based on whether their linked Atlas projects are "At risk," "Off track," or "On track."

This has broken portfolio reporting workflows, particularly for customers using Jira filters to power Confluence reports, as the deprecated status fields now only contain stale data and do not reflect live Atlas project states.

Proposed Solution:
Provide a mechanism within JQL to query Jira issues based on the sub-properties (specifically Status) of the native Atlassian Project field.

Example JQL Syntax:

• AtlassianProject.status = "At Risk"

• AtlassianProject.status IN ("At Risk", "Off Track")

Use Case:

• Project managers need to identify all Jira issues associated with projects that are currently "Off Track" to prioritize resources.

• Portfolio leads need to generate Confluence reports that dynamically display work items linked to "At Risk" initiatives.

Additional Context:
This request stems from the deprecation of the atlasProjectStatus field and the current inability to query sub-properties of the new native integration field.