I am having an issue where a set of issues are missing from my Portfolio scope. By reading Configuring the scope table in the troubleshooting, it looks like it is because I am excluding some of the Releases from the plan. This is done on purpose as we have a boat load of releases defined, but I don't want to track those to a plan, but I still want to track the issues that are associated with them.
First, am I interpreting this article correctly?
Second, is there a way to get these issues into the plan without adding in all the releases associated with the projects?
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
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