-
Suggestion
-
Resolution: Unresolved
-
1,650
-
34
-
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
-
- Closed
-
- Gathering Interest
-
- Future Consideration
[JRACLOUD-89892] Extend functionality of portfolioChildIssuesOf() to improve searchability
This is the single largest frustration among the PMs I work with. It's infuriating that you can't do this via quickfilter.
We are starting to use the Initiatives issue type, so having this functionality to search for Initiatives that are parent of issues within a range of projects, by key, would really improve the usability in plans, by building over a filter like this.
The main issue with nested JQL queries, and something to keep in mind is that they can be abused and create high load on the system. If Atlassian was to implement this, they would have to take that into consideration.
—
An automation workaround that may assist with some of the use cases on this JAC ticket.
We created an automation that copies the grandparent information from the parent into the child issue.
Eg:
The automation picks up the parent field from the Epic and then populates a field on the Story.
This then allows for JQL searching on the Story using the grandparent Initiative as a JQL filter.
Hope this helps someone.
Throwing support behind this
We have a use case where the demand is to update all children of tickets for ANY Epic or Initiative whenever the Components are updated, not just a specific Issue. It needs to be an issue type level function. Example #2 in the Desired Results would be a great way to implement this ask.
Currently A4J allows for a single child ticket to be updated by issue type but not all the way down the hierarchy.
+1
We urgently need this function to be updated with also supporting issues from team-managed projects.
Our use case:
We want to plan a huge initiative with Advanced Roadmaps/Plans. There are several projects (company- and team-managed) participating in this initiative which already contain hundreds to thousands of issues, but only 10 - 100 of them belonging to the initiative. When I now include the whole projects into my plan, I will reach the issue limit (5.000) pretty fast, so I would have to narrow down the included issues with a proper filter query. Unfortunately, without portfolioChildIssuesOf(), I don't find any filter query which would meet my needs: showing all issues through the whole hierarchy (initiative -> epic -> story/bug/task -> sub-task) belonging only to my planning-projects initiatives.
So I really need this function to include also issues from team-managed projects.
In the same context I'd also be very happy to see option #2 being realized to include all our initiatives in one easy function call, but I might have a workaround for this issue: I'm thinking about creating another hierarchy level above initiative, create one issue of this type and per default link all my initiatives to this one ticket. Then I would have to call the porfolioChildIssuesOf()-function only for this one ticket and keep it kind of dynamic for upcoming issues in the underlying hierarchy.
This request was raised almost 2.5 years ago. Still not implemented
Please this is the basic functionality. This will help us to create a filter much easier for product owners. please get this feature ranked up.