Background: My team uses a single Jira project for all activities. For a particular activity, we are tracking 5 Epics and their respective sub Issues.
Challenge: As I understand it, the default behavior for the Roadmap macro is to slurp in all Epics in the project. To constrain the Roadmap to select items, one needs to create a new Board, then base the Roadmap on that Board. I created a new Board with the following:
issueKey in (MKT-327, MKT-338, MKT-345, MKT-360, MKT-367) ORDER BY key ASC
This represents each of my Epics perfectly fine in the resulting Roadmap, however, my challenge is the child Issues are not present. I was assuming, perhaps erroneously, that the Epic items would be able to expand and collapse but that is not the case.
Thanks in advance for the recommendations
Your query limits the data to just your epics so the roadmap has no stories to show!
I would add
Or (project = mkt and issuetype != epic)
Thanks for the quick reply, @Nic Brough -Adaptavist- . But won't that return every item in the Project that is not an Epic? I would need the query to constrain to the Epics defined in my initial query, along with their respective child Issues and subTasks, right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that's the point. The roadmap only works off the issues you choose for the board. If you hide them from the board, the roadmap can't display them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gotcha. I figured out a simple query. Works great. Thanks again for the guidance. Here's my query in the event someone is searching to figure out the same:
project = MKT AND parentEpic in (MKT-327, MKT-338, MKT-345, MKT-360, MKT-367) ORDER BY created ASC
Results in a pretty Gantt like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Excellent, that's a couple of steps forward from my "and issuetype".
I looked at issue type to try to illustrate why stuff wasn't coming out in the context of your starting point. Project and parentEpic is a far better way to do it here!
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.