Let me say up front that we have recently upgraded Jira from data center 8.18 to version 8.22.3, so it is not clear how that affects the issue I am describing. The roadmap Configuration process has changed significantly with v8.22.3 - teams and releases are now separate tabs whereas they used to be a part of the Configuration process.
I am working to understand the hierarchy of how Jira selects the stories and epics to be included in a roadmap. I have numerous teams/boards and releases that are included in the roadmap, but the content that I want to see is tightly defined by a Jira filter.
However, I end up with hundreds and hundreds of stories in the "Issues without parent" list, and I think this happens because of selecting all of the teams and their pertinent releases. This causes a lot of manual work to either 1) find an isolated story that should be included in the plan so that you can "drag it up" to display properly (somewhere above the "issues without parent line") or 2) to perform the "remove from plan" action to have a cleaner view or the roadmap.
So, I am wondering...
1. Can I make the roadmap based solely on a filter without having to select teams/boards and associated releases? I have tried (unsuccessfully) to do this, so I think the answer to this is "no," just confirming that I am not missing something.
2. As an alternative can I make the filter the first level of selection and then have the teams/releases applied after a subset is created by the filter? Or are the selected teams and releases and the defined filter all applied separately?
All feedback is welcomed.
Thank you.