Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,474
Community Members
 
Community Events
176
Community Groups

Locking down a single project fix version

We have a team that is more waterfall in nature that's looking for a mechanism to control a fix version's scope

  1. Only a chosen group (e.g. management) can adjust what goes in/out of that fix version, preferably w/ an audit trail
  2. However, other issues can be freely assigned to other fix versions

Thanks!

1 answer

0 votes

Hey Yen,

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.

Cheers,
Rhys | Portfolio for Jira Product Management 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events