nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Epics' parent Initiative not showing up in Plan

Prashantha_wf7qee

I created an Initiative - 112 in Proj-1 ; and then I created two Epics - 113 (in Proj-1 linked as a child to 112 - Initiative) and 1415 (in Project-2 -linked as a child to 112),

I also created a couple of stories in 1415 (epic)

When I create a plan with filters (all the issues have a component - Release-x), I see that Epic-to Story is showing accurately as descendants

but Epics themselves are showing up as issues without parents

Accepted answers

All comments

Magdalena Zhisheva

Hi @Prashantha ,

Have you tried to click on Filters -> Hierarchy -> From to be Initiative?

Hope it helps!

John Elder

In addition to Magdalena's point to check the hierarchy filter... I also am thinking that this is related to how JQLs can not be nested under each other in the same query. I haven't found a way, via filter, to pull in the children of an Initiative, and then also pull in the children of those child Epics.

I have only seen it work using a Board(s) as a Plan source, rather than a filter. Just my experience, however, and I could be wrong.

Prashantha_wf7qee

Yes, I have

Prashantha_wf7qee

I tried that as well, finally someone advied me to move the Epics manually (drag and drop) under Initiative..and that's what I am doing now.

John Elder

Make sure to leverage the "Parent Link" field within Epics, so the parent/child link is "official". Otherwise, the hierarchy you are setting up will only be 'viewable' in Plans.

Brad Lackey

I was able to resolve this by adding the Initiatives project as an Issue Source. But I do not have the Initiatives in the hierarchy under Filters...so that the initiatives don't populate in the plan...just the parent field.

kmeyerer

This is more nonsense Jira behavior, the Parent field isn't treated as a value (wherein if it's populated, the information just displays, like it should), the parents have to be included in your query parameters.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud