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?
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Recently, as part of a series of Portfolio for Jira case studies, we spoke with Carl DiClementi, Director of Product Management at Factom about how he uses Portfolio for Jira. In...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs