How to prevent new epics/stories from automatically being added to portfolio plan
Asked by Jasper van de Peppel:

When setting up a new portfolio plan over 4 different teams (projects), I've created a new cross-project release and added some epics for each team which are needed for this release. Now, the teams can add stories during refinement and so on.

When I took a look at the scope of this plan a week later, I suddenly see new epics and stories in the scope of this plan. I see no link to releases, initiatives or anything else, other than these are created in the projects of the teams in this plan. Is there any way to prevent this?


Answers:
author: Thomas
body: Hi [@Jasper van de Peppel](/t5/user/viewprofilepage/user-id/1158410),

Portfolio plans issue sources can really be summarized as a JQL filter and, as you noticed, new issues appearing in the instance might match the filter. If you want to look at a very specific scope that does not include epic created later on I would suggest using JQL filter issue source that filters out also based on creation date and potentially on parent / epic link.

If you are on Portfolio for Jira server I would also consider filtering using the [childIssuesOf JQL function](https://confluence.atlassian.com/jiraportfolioserver/searching-for-issues-using-portfolio-details-940678957.html).

Cheers,

Thomas

comments: author: Dan Silver
body: Hi [@Thomas](/t5/user/viewprofilepage/user-id/58170) -- is there a plan to fix this? The user experience is \*painful\*.


author: Thomas
body: Hi [@Dan Silver](/t5/user/viewprofilepage/user-id/1185451),

I'd suggest upvoting and sharing your use case on the related feature suggestion here: <https://jira.atlassian.com/browse/JPOSERVER-1706>

Cheers,

Thomas


author: German Di Napoli
body: [@Thomas](/t5/user/viewprofilepage/user-id/58170) how we can use JQL filter in Jira Portfilio? When you define a plan I didn't see any option and only can select the project, releases, etc


author: Thomas
body: Hi [@German Di Napoli](/t5/user/viewprofilepage/user-id/1715401)

The actual issue sources of Advanced Roadmaps (aka Portfolio) can be a combination of Projects, Boards (which are backed by a JQL filter), and JQL Filters.

You can have a look at [this video tutorial](https://youtu.be/9cBCwnMToXQ?t=50) for some more details on this or the more complete [product documentation](https://confluence.atlassian.com/jiraportfolioserver/creating-plans-952623582.html).

When it comes to doing some Additional filtering on top of existing issue sources, we provide many in-plan [filters](https://confluence.atlassian.com/advancedroadmapsserver/filtering-issues-962968235.html) but JQL is not currently available.

We are currently looking at ways to improve our plan creation experience which would introduce new ways to filter upfront.

Cheers,

Thomas


author: Brian Dawson
body: I'm having the same problem? did this ever get resolved? Or did you find a work around?

comments: author: Jasper van de Peppel
body: Nope, no solution found. Portfolio is made to 'help' you in certain ways apparently and if your company's way of working or organizing work doesn't comply to that, you're out of luck.


author: Brian Dawson
body: Thanks [@Jasper van de Peppel](/t5/user/viewprofilepage/user-id/1158410). Yes it's a painful experince to have to constantly remove epics that get added for other initiatives. I may need to consider a different solution.


Tags: advanced-roadmaps