Summary

The JQL function issuekey in childIssuesOf() is seems to be very expensive when dealing with larger result sets and will easily take up to if not over 2 seconds to finish for a single parent key if the customer uses multiple childIssuesOf() functions within a single JQL filter the search will take over 10 seconds which can lead to some problematic behavior.

Steps to Reproduce

1. Link 200 issues to a single initiative.
2. Search for the child issues of the initiative.

Notes

If you capture the behavior within a HAR file you may see a jqlTooComplex error, however this appears to be a false error as the results are still displayed correctly.

Workaround

Currently no workaround known.