You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi,
my plan is based on several Jira boards. From these boards I am interested in scheduling some issues (issue 1, 2, 3) of a release (release A) in Portfolio for Jira.
When new issues (issue 4 and 5) are added to a release (which is included as an issue source), I don't want these issues to show up in the scope. Is it possible to freeze the scope, so that no issues are pulled, no matter what?
Thanks and regards,
Phil
Hi Scott,
thanks for the answer.
I like your suggestion and am pretty sure that this would work. Unfortunately we are not allowed to introduce new custom fields in our project.
Based on your idea I searched for (and found) an existing field that helped me to set a filter that excludes the redundant issues.
Thanks and regards,
Phil
Great, I'm glad I was able to help! Could you mark the answer as "accepted" so others can find it more easily?
-Scott
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
(Thanks!)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Phil,
I'm new to Portfolio, so this may not be the best way to accomplish this, but here's my suggestion anyway....
This should keep your Program limited to the initial scope of the projects while allowing new issues to be added to a project.
One caveat though...Like I said, I'm new to Portfolio, so i don't know if adding issues that are not part of the frozen scope would have an unintended consequence to the program. I can think of a scenario where a bug or sub task is added to the project that causes an issue from the scope to be delayed or moved to a later sprint, which could impact your program's timeline.
If you try this make sure you test it out...and post the results here. If it works, please mark the answer as "accepted" so others can find it.
Hope this helps,
-Scott
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.