filter JIRA on parent link not in (liste off deature) doesn't work
ex :
project in (VSMPBEB) AND "Parent Link" not in (PP2-2043, PP-2048)
how can i do this filter ?
thank you
Hello @cknitzeff.laposte ,
When searching on the portfolio "Parent Link" it will allow for the operators in Jira Server:
Check out the following KB article for more details on the search capabilities on Jira Server:
(!) Important Note: the KB above is specific to the Server platform, and there are different options for Cloud, which does currently have a "NOT IN" operator, If anyone does run into this Thread looking for similar functionality on the cloud platform please refer to THIS KB instead as the options here do vary across the platforms.
So, as there is not an option to do a "Not In" operation for parent link on Jira Server to exclude certain issues the field referance will rather be tied to the Queries on operation that are inclusionary and looking for issues that are linked to a specific values OR Empty OR Not Empty via the "Is" and "Is Not" operator options that can only be used with an "Empty" variable.
A different approach that I believe would work for this would be to leverage issuekey not in childIssuesOf("") mentioned in the KB above to exclude the issues that are children of the parent issue, and do something like the following:
(issuekey not in childIssuesOf("PP2-2043") AND issuekey not in childIssuesOf("PP-2048")) AND project in (VSMPBEB) AND "Parent Link" is not EMPTY
The Query above will exclude all the child issues that have a parent link to the specific parent initiatives, in the desired project, and only show issues that have a parent link associated.
However, there is some additional behavior to be aware of with the Empty variable related to how the parent hierarchies work across multiple levels of issue types, as the Parent Link field in Portfolio is not a standard field but rather a collection of information about various fields stored as a json value in the database via the property_entity table specific to Portfolio hierarchies and independent from jira native field behavior. The following Feature Request discusses this a bit more for cloud and server respectively:
Additional Feature Requests that relate to this and also offer some notes on JQL formatting to get the desired results that I would recomend checking out can be found here:
Noting the primary concept of what is occuring:
This happens because the "Parent Link" search keyword is an abstraction of parent links, going beyond the actual custom field with that name.
AND
Searching for_ Parent Link _actually searches for the CONCEPT of Parent Link, meaning it considers all three possible links: Issues (subtasks) with parent issues Issues with Epics Issues with Parent Links (the JPO custom field itself)
Searching for_ Parent Link _actually searches for the CONCEPT of Parent Link, meaning it considers all three possible links:
So, you may need to rework the query example I noted above a bit depending on which hierarchy levels you are looking to return in the data set. But check out the Examples on the Feature requests in the Workaround sections for the alternate formatting options contingent on hierarchy levels you are looking to expose.
Regards,Earl
It looks like you're new here. Sign in or register to get started.
