Descendant search in JQL using portfolioChildIssuesOf() will include team-managed space hierarchies

Starting February 1, 2027, we'll progressively roll out a change to the portfolioChildIssuesOf() JQL function so its results include work items in team-managed spaces. Today, the function only follows hierarchy in company-managed spaces, so searches can miss descendants that live in team-managed spaces.

What's changing

• portfolioChildIssuesOf() will return descendants through valid team-managed space hierarchies, including supported relationships between company-managed and team-managed spaces, such as a team-managed epic under a company-managed initiative.
• Queries that use NOT IN portfolioChildIssuesOf() will exclude these additional work items.
• Results continue to respect hierarchy rules, user permissions and issue security.
• REST API request and response formats don't change.

What you need to do

If your app, saved filters or automation rules assume that team-managed work items are excluded from portfolioChildIssuesOf() results:

1. Find the queries that use portfolioChildIssuesOf().
2. Check whether team-managed work items in the results would affect your logic.
3. If they would, update your queries or result handling before February 1, 2027.

We'll publish another update when the rollout starts.