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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a build plan configured as 'Important' and another configured as 'Default' with the expectation that all the jobs from 'Important' plan get priority in the build queue and put on the top of queue.
This doesn't happen always and the jobs from the 'Default' plan continue to stay on the top when a 'Important' job is added to the queue
*I did ensure, the priority is set accordingly not just at the Plan level, but also at the job level*
I have the same issue. When a build is started the jobs go into the queue and some with default priority are on top while some with urgent priority are below. Do I need to restart Bamboo or something to apply the change?
In our case the plans priority is default and some jobs in this plan were changed to urgent.
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.