-
Suggestion
-
Resolution: Unresolved
-
280
-
21
-
It would be great to have the same option which was released to serve in 2.11 Release available in Cloud.
To quickly pull up parent or child issue of an issue via JQL and search issues within Portfolio hierarchy.
EXAMPLE:
For parent issues of an issue
- For parent issues of an issue in a specific hierarchy level in Portfolio for Jira, type issuekey in parentIssuesOf("EX-000").
- For instance, you have this hierarchy:
- INIT-001 (at initiative hierarchy level)
- EPIC-001 (at epic hierarchy level)
- EPIC-002
- INIT-001 (at initiative hierarchy level)
-
-
-
- STORY-001 (at story hierarchy level)
- STORY-002
-
-
- To get the parent issues of STORY-001, type issuekey in parentIssuesOf("STORY-001"). All parent issues above STORY-001 will be returned, and not just the immediate parent issue at the epic hierarchy level. This means EPIC-002 and INIT-001 will be returned.
For child issues of an issue
- For child issues of an issue from a specific hierarchy level in Portfolio for Jira, type issuekey in childIssuesOf("EX-000").
- For instance, you have this hierarchy:
- INIT-001 (at initiative hierarchy level)
- EPIC-001 (at epic hierarchy level)
- EPIC-002
- INIT-001 (at initiative hierarchy level)
-
-
-
- STORY-001 (at story hierarchy level)
- STORY-002To get the child issues of INIT-001, type issuekey in childIssuesOf("INIT-001"). All child issues below INIT-001 will be returned, and not just the child issues at the epic hierarchy level. This means EPIC-001, EPIC-002, STORY-001, and STORY-002 will be returned.
-
-
Release link:
- duplicates
-
- Gathering Interest
- is related to
-
- Gathering Interest
-
VOLTRONPRJ-938 Failed to load
- is resolved by
-
JPO-24770 Failed to load
[JRACLOUD-89056] Quickly pull up parent or child issues of an issue via JQL and search issues within Portfolio hierarchy in Jira
I am getting error "unable to find JQL function 'childissuesof' . Please advise.
I am missing a possibility in JQL to test if an issue has a Parent. I need to find all issues that has a Parent using JQL, similarly as using IssueLinkType in ("split from") to get all issues that has a Split From link.
Just in case it benefits anyone, most but not all of what I am watching this issue for is now supported by
parentEpic in (EPIC-1, EPIC-2, EPIC-3)
in Jira Cloud without using other addons to support it, I realise that this isn't all that all are asking for, eg. I have to get the comma-separated list of Epics together first rather than being able to write JQL between the brackets, but after moving from cloud where "epic link" in (EPIC-1, EPIC-2, EPIC-3) was so intrinsic to how I was filtering, this was a massive step forward when I discovered it in November
(My response to Atlassian : https://support.atlassian.com/requests/MOVE-146157/ “@Rananjay this DID help but slightly by chance, because ParentLink DIDN’T do what I wanted, but ParentEpic DID, so please close and please ensure anyone else with same query knows about ParentEpic as likely means they won’t then be left waiting for https://jira.atlassian.com/browse/JSWCLOUD-19543 or considering paying for Premium when not required for ParentEpic to work.. Thanks, Tom “)
Anne, while you are correct, it's not the intent for this request, which is to return the complete hierarchy (up or down) of an item, and I don't want to let Atlassian devs off that easily. 
The crucial differences in my eyes are:
- Being able to traverse more than a single level of hierarchy within the one query
- "Parent Link" only provides Epic down to first children, not up to initiatives nor all the way down to sub-tasks
- Being able to go all the way from top level to bottom, and vice a versa
- And, probably most importantly, it's inclusion in the basic (not premium) product
- I don't have "portfolioChildIssuesOf" available to me
While I appreciate (not necessarily agree with) Atlassian's perspective on nested JQL queries being an advanced feature, being able to get all levels associated to a Initiative, Epic, Task (or similar) I believe to be a basic level of functionality. ie, if I have this top level thing, show me all it's lower level things. And, if I have this low level thing, show me the branch all the way to the top. As a stretch goal, and not mentioned in the original request; given this thing in the middle, show me all the lower level things, plus the branch all the way to the top - in a single, non-nested query.
</2 cents>
Hi all,
For the descendants of an issue, you can use
issuekey in portfolioChildIssuesOf()
More details can be found here: https://support.atlassian.com/jira-software-cloud/docs/search-for-advanced-roadmaps-custom-fields-in-jql/
Thanks,
Anne Jang
I just cannot believe this seemly very straight forward feature is still not available ever since Portfolio was acquired by Atlassian back in 2017?
This makes Advanced Roadmap half dead for adoption by organizations that are running 5000 - 10K issues for annual or semi-annual releases.
The child version of this exists as: issue in portfoliochildissuesof("issuekey")
Above mentioned way of finding issue details is not worked for me it is deprecated.
I have use this "jql": "'Parent Link' = ABC-120" and it work for me.
Read this document - https://confluence.atlassian.com/jiraportfoliocloud/searching-for-portfolio-for-jira-custom-fields-in-jql-941619014.html
Hi 35ceda9a3870 , this is because this is a feature request and under consideration.
I don't know your use case but there is this option you can use:
issuekey in portfolioChildIssuesOf(ISSUEKEY)
or for just always one level down with
parent = ISSUEKEY