We're using Bamboo 5.3.0 and I would like to know the purpose of the "Approved" or "Broken" button options for each deployment release, specifically, the purpose of their current implementation.
The obvious problem is that there is no way to restrict/permission who can or cannot click on them. It's just a toggle button that anyone can click on. Should be that only specific groups (QA) or users can click on this.
So once the permissions are in place, then it would make sense to have only "Approved" releases be able to be deployed to the next environment (e.g. Staging is Approved, now we can deploy to Production) and alternatively, "Broken" release cannot be released (even to the same environment) until it becomes "Approved"
Community moderators have prevented the ability to post new answers.
I'd really like to see this implemented as well, so I've created a feature request for it, please vote for it here: https://jira.atlassian.com/browse/BAM-15814
Thanks Austin.
I did "+1" to your request with my comments.
Really hope this will make it into Bamboo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Thank you for your question.
The Approved and Broken buttons are just flags that work as labels, but more exposed. They are not used anywhere in the logic, I am afraid.
If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.
Thank you for your understanding.
—
Kind regards,
Rafael P. Sperafico
Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yo, thanks for the explanation but seriously that button in Wak. You really should be able to trigger builds / deploys following that action or block builds missing that approval, seems like a great feature that was partially implemented
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"great feature that was partially implemented" .... yeah, well, welcome to Bamboo!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Will this feature/functionality will be implemented in future release of bamboo? I see many users (QA) who sees this functionality very useful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
Any plans go forward for fully implement this feature?
Cheers,
Gonchik Tsymzhitov
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here we want our release manager be able to approve it and then it generate a final release -> deploy it on some platform and so on !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1 and setting to Approved or Broken should be able to trigger a subsequent action, e.g. tag/label source repository promote artifact internallly promote artifact externally (e.g. in Nexus)
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.