Issue Summary

Using a JQL query with portfolioChildIssuesOf function with an issue key that contains too many children(and/or grandchildren), will return no results.

issuekey in portfolioChildIssuesOf("Parent key with +500 children")

Steps to Reproduce

1. Create a parent issue and add hundreds of children and grandchildren*
2. Run this JQL query for this parent key

   issuekey in portfolioChildIssuesOf("Parent key with +500 children")

   *Unsure what is the magic number to reproduce this issue, but you might need hundreds of grandchildren as well.

Expected Results

JQL returns the issue keys successfully.

Actual Results

JQL endpoints return 200 OK but 0 results due to backend error.

Workaround

• Sometimes the intent of using portfolioChildIssuesOf is to get the direct child from a given parent key; for these use cases, you can use the new Parent field instead.

  parent = <issue_key> 

  Remember that in the default Jira setup, if you run this query for an Epic, it will return all stories below the Epic, but it does not return sub-tasks from all the stories as the portfolioChildIssuesOf does.

• Having too many children can impact even the usability since issue view can only display 500 children issues. Reduce the number of child issues by splitting the parent issues