Versions: This filter allows you to screen issues based on the released product versions. For example, the product features that you have released through different versions. Epic: This filter allows you to group deployments and issues by epics. You can also filter the issues that don’t have a parent epic.
if you want a board that has Epics and Child issues then yes. if you want an epics only board you can do that with a filter and your roadmap would be only Epics as well as your Kanban board. Sounds like you want one board to manage it all in which case the swimlanes makes the most sense to me and it is a super easy change on the board config.I would think you could use the following. The first part covers the actual epic issue keys and the second covers the issues that are part of those Epics. Thank you Jack , I am awaiting the users exact JQL. So they are trying to exclude Epics that are part of an Initiative. The Initiative is the parent of the epic and used the field Parent link
Hi. I am relatively new to Jira so struggling a bit with JQL. I want a filter where I want to see all issues except those with a parent epic is in Status hold. Something like.. project = XX AND status in (x, x, x, ) AND Parent epic status is not on hold. Can I do this is standard JQL?
Indeed, Jira automation does not have a function to remove a component of a child issue (Stories, Sub-task, etc) when it gets removed in the parent issue (Epic or Parent task). We have the following feature request to get this function implemented on the rule triggers, so you would be able to use the Smart values to properly reference it in the . 265 47 394 282 214 269 364 83 116