Hi,
I'm trying to generate a list of parent issues where all underlying child issues have the status Done.
Some preamble and context:
- All parent issues have the issuetype Business Epic (not to be confused with issuetype Epic)
- These issues are themselves linked to Initiatives
- All child isses have the issuetype Feature
- All these relationship are defined through the custom field Parent Link
I ended up with something like this:
project = "business epic project" AND issueFunction in LinkedIssuesOf("project in (featureproject 1, featureproject 2 etc) AND status not in (Funnel, Review, Analysis, Backlog, Implementation)")
Result is a list of parent issues that contains at least one child issue with status Done. However, it doesn't exclude parents issues with other child issues with a different status. E.g. resulting list also includes parent issues with, for example, a child issue with status Done and a child issues with status Implementation.
Is there any way to exclude all parent issues where a child issue has a different status than the desired one?
Thanks in advance!
You can also use "not in" to negate the result for any other conditions. So it could be similar just with not in { list of unwanted statuses }.
But you will probably have a lot of trouble maintaining filters like this. If you were to focus on resolution empty/not empty, that would be more robust.
Hi Radek, thanks for the reply!
With regard to resolution instead of status: Fair enough.
With regard to using "not in": that is indeed what I tried, unless I misinterpret your suggestion.
However using "status is not { list of unwanted statuses }" or "resolution is not EMPTY" results in a list of issues that has at least one child issue that has the wanted status or a resolution. A parent issue where the underlying child issues have multiple statuses will still be shown as long as one of those has the status Done or a resolution, whereas I try to make a list of parent issues with only child issues in Done or with a resolution.
Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Noooo no, there is a way to do it, there has to be by principle.
You're filtering out issues based on conditions "A".
If you use an AND not condition "B" - then "B" effectively filters out that which you don't want.
Unless I misunderstand the question.
It's also the 'linkedIssuesOf' that I'm skeptical about. If everything here (Feature <=> Epic) is using Parent Link, then 'portfolioParentsOf' is a better fit since it does not include any other random issue links that might be occurring anywhere. This function works with Parent Link (as well as subtasks and epic links).
That being said, if the original query is
project = "business epic project" AND issueFunction in LinkedIssuesOf("project in (featureproject 1, featureproject 2 etc) AND status not in (Funnel, Review, Analysis, Backlog, Implementation)")
I think you should be able to achieve the result with something like
project = "business epic project" AND issueFunction IN portfolioParentsOf("project in (featureproject 1, featureproject 2 etc) AND status not in (Funnel, Review, Analysis, Backlog, Implementation)") AND issueFunction NOT IN portfolioParentsOf("project in (featureproject 1, featureproject 2 etc) AND status in (Funnel, Review, Analysis, Backlog, Implementation)")
It's a straight up negation of the condition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I see what you mean, Radek. The initial query seems to have missed an explicit excluding condition, the "B" to the initial "A". I've tried your suggestion and it seems to indeed return the desired list.
Thank you for your explanation!
Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.