In 2.6.5 I see that the “Promote” button with a dropdown vs the “Deploy to…” button is being extremely inconsistent as to what environments it thinks the user has access to.
I really hope this is just a UI bug and not a permission bug, so that random developers can’t in fact deploy to live if they click it.
Please see attached pictures.
You can see that both dialogues thinks my test has access to 5 environments (which is correct=. But in one dialog it has replaced “Dev” and “Test” with “Verification” and “Live”, which that user most certainly has no access to other than seeing what release is deployed there.
Thanks for reaching out. The user can “see” the environment on that list because he has access to see what releases are deployed there. As soon as the user tries to deploy to that environment, Octopus will validate if the user has permissions to deploy to it, and the user will get an error message.
