Why doesn't the advanced roadmap show expansion arrows for all epics?

[Kurt Smith]

I've set up a plan that uses a query to pull in several epics but the expansion arrow is only showing for one of the epics

[Trudy Claspill · Accepted solution]

Can you show us a screen image of the roadmap, and the filter you are using?

[Kurt Smith]

As you can see Epic 895 has more than one story but is not presenting with an expansion arrow in the Plan.  Also, why don't Epics with one story present an expansion arrow?

[Trudy Claspill]

Can you show us the filter you are using for this roadmap?

[Kurt Smith]

Yes, sorry, here it is:

project = OPS1 AND issuetype in (Epic, Story) AND status in ("In Progress", "QA In Progress", "To Do") AND text ~ MPDT ORDER BY cf[10020] ASC, created DESC

[Kurt Smith]

The problem is the query.  Can someone help us develop a query that will pull all Epics with MPDT in the summary and then all the stories assigned to those Epics?

[Trudy Claspill]

Do you have any Jira JQL extending marketplace apps available in your Jira instance?

Jira's native JQL functionality can't build the filter you need.

[Kurt Smith]

We found a way to fix this for now...

[Trudy Claspill]

Can you share your solution?

[Kurt Smith]

project = OPS1 AND issuetype in (Epic, Story) AND status in ("In Progress", "To Do") AND (labels = MineEng OR summary ~ MPDT or summary ~ AU) ORDER BY issuetype ASC, priority DESC, "Epic Link" ASC, created DESC

We put labels on the stories and then used the above query...works fine in the Plan now