Ability to filter by parent epic status?

[Andrew Grossman]

Hello!

I'm looking to create a filter that displays tasks where the associated epics are in a particular status. Specifically, we have development tasks that we want to exclude from a board until the parent epic has been moved into a state indicating it is ready for development.

Is this possible? I see some related-looking questions referencing using perhaps parentEpic() to do some filtering, but those all look like solutions where the epics are being specified by key rather than some field condition.

I might have thought this would be where "Epic Status" would be used, but the basic filter feedback claims it's not applicable here. Maybe it's because that's the separate status with options associated with epics?

[Bill Sheboy · Accepted solution]

Hi @Andrew Grossman 

JQL is not a SQL, and so does not support the nested/correlated query syntax needed to do what you ask.

Some options to help your use case are:

• buy: investigate marketplace addons for purchase that enhance JQL
• replicate data: use automation rules based upon changes to the epics to somehow mark the child tasks as "ready for development", and then update your board filters appropriately
• process change: pause to consider how work is being made visible on a board prior to its parent epic being ready.  Then improve your Sprint planning (or Kanban queue replenishment) so only ready work is pulled for start.

Kind regards,
Bill

[rkianian]

Hi  @Andrew Grossman 

Did you test any of these options? I'm looking to do the exact same thing and I'd love to hear what worked/didn't work for you. 

Thanks, 
Rojin 

[Andrew Grossman]

@rkianian Sorry, I don't recall where I landed on this. I actually think that I found articles demonstrating some sort of cascading filter capability at some point but my team just gave up on it due to the lift involved. We've moved to a hybrid approach where we manage our epics in Airtable and use that to drive our task selection.

[rkianian]

@Andrew Grossman Ok, thanks for the update!