The field "parent link" as exposed in JIRA Portfolio does not seem to be apparent to JQL queries. How do you search for epics that are linked to the same parent Initiative?
Hi @Maria Mallorquin Canet.
What's the ETA on that? We're trying very hard to implement SAFe on JIRA and Portfolio, and are using the Parent Link. However without this we can't filter "SAFe Features" (JIRA Epics) based on their Parent Link (to "SAFe Epic/Initiative"). Should we abandon this approach, or is there a hack or a issue.property we can use, or is it likely to be released in the JQL search in the next week or two?
Parent link JQL functionality has been implemented as part of Portfolio 2.1 which released on the 7th.
You can filter for your SAFe Features based on the Parent link by searching for the issue key (e.g "Parent link" = INIT-1).
Note that the interface behaviour has some inconsistencies with how searching for Epic Link works. 1. The issue key needs to be in all caps.
2. You can also type the Initiative/SAFe Epic name for suggestions but they won't appear unless you have complete words (won't search for substring of words).
Please let me know if you're having any problems with this.
Hi Rhys. Thanks for such a quick response, much appreciated.
Unfortunately I can't seem to get JIRA "Search for Issues" to accept this JQL, but I have put the Parent Link issue type in scope of all projects etc and am succesfully linking them in the create/edit of the child, and showing the children in the parent issue, and they are reflecting in Portfolio. So it's strange that I can't search for issues with a certain parent-link (even though I know the link is there, with many child issues below it).
We are on JIRA and JIRA Portfolio Cloud so should have all the latest updates.
And have tried with "Parent link" = ITAMPPF-49 and a few other variations, single quotes, no quotes, but no joy.
Perhaps, is there a underlying field code that could be used, such as
but I have no idea what the field code is.
@Rhys Christian, I've looked at our cloud add-ons, and notice our Portfolio for JIRA is Version 2.0.9 (not 2.1.x as per your comment above).
Is 2.1 not yet fully rolled out to all Cloud instances yet perhaps?
Apologies, I should've mentioned this feature isn't yet available on Cloud.
Releases for cloud were held back during Summit. 2.1 is expected to be available for Cloud this week.
Interesting how the "What's New" page shows this was released to Cloud on 7th October (Version 2.1.2-OD-001 as you advised)
10 days later we still don't appear to have this release in our instance
Do you know if there's a page that shows the rollout schedule for "regions", "zones" or nodes if such things exist in Atlassian Cloud?
You're are right, we just noticed there was a mistake on the release notes that has already been fixed. The version that includes parent and teams field searchable via sql hasn't been release for Cloud yet.
Sorry about the confusion.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events