-
Suggestion
-
Resolution: Unresolved
-
1,810
-
41
-
Summary
Currently, portfolioChildIssuesOf() only accepts one input parameter in the form of an issue key. This makes searching for child issues of multiple parents unwieldy, and doesn't allow for flexible search of child issues based on other parameters. This function also does not include team managed projects.
Desired Results
Either or both of the below results would increase usability of the function and it would be great if this function also returns team managed projects which can be child or parent of an issue.
- Allow the function to accept multiple issue keys as a comma separated list. E.g., issuekey in portfolioChildIssuesOf("EPIC-001", "EPIC-002", "INIT-001") returns all child issues of EPIC-001, EPIC-002, and INIT-001.
- Allow the function to accept a subquery within JQL. E.g., issuekey in portfolioChildIssuesOf(project = ABC and issuetype = Epic and environment = "Desktop") returns child issues of Epics in the ABC project with a specific value in the environment custom field.
- relates to
-
JRACLOUD-78912 JQL function to filter child issues of an Epic
- Closed
-
JRASERVER-70710 Filter to return child issues of Epics meeting certain conditions
- Gathering Interest
-
JSWCLOUD-19543 Quickly pull up parent or child issues of an issue via JQL and search issues within Portfolio hierarchy in Jira
- Future Consideration