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
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
We have a team that is more waterfall in nature that's looking for a mechanism to control a fix version's scope
Thanks for the question. If I understand correctly you want to prevent the Scheduling output from calculating issues into certain fix versions - which happens when there’s free capacity in your release to add more work and you’ve issues not assigned to a release.
Unfortunately the functionality you’re looking for isn’t available for releases with a fixed end date. I suggest you vote and watch this ticket to express your interest and receive updates: https://jira.atlassian.com/browse/JPOSERVER-1575
If you don’t mind the trade-off, a workaround may be to use Releases with ‘dynamic release date’ for those management defined releases as they will not have new scope added to it. However you lose the functionality of being able to calculate the viability of the release or display a set end date - the end date will be based on the calculated end date of your explicitly selected scope.
Please let me know if you have further questions.
Rhys | Portfolio for Jira Product Management