I'm curious to get the community's input on ways they have approach this use case in Advanced Roadmaps.
We have `Initiatives` which are collections of Epics from one or many projects in Jira.
When a Program manager sets out their plan they use the `portfolioChildIssuesOf` function as a Filter Issue Source for all of the scope they are interested in viewing/planning. It will automatically gather up all the relevant issues based on parent links. In most cases this is a narrow sub-set of issues from a series of projects.
The problem with this approach is it doesn't show any Sprint planning details for any stories. To show this you must add additional Boards/Projects issue sources to the plan for any of the projects in scope of the program.
This works however there is a side effect that additional cards not relevant to the particular PMs work start appearing on the board. These issues can be removed from the plan but this continues to be a manual tasks as more and more issues are added.
For now I've just learnt to ignore any `Issues without parent` though for some larger plans this becomes a performance/noise obstacle.
Does anyone else have this problem? What is the best Approach for restricting the scope of a plan around a point in the issue hierarchy while still seeing sprint info?
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events