Approved/Broken not useful on Deployments

dustin_barnes March 31, 2014

If you're anything like any company in the world, you release to QA, then that build, when approved, can move to Stage. From there, another approval, and it moves to Prod. There is now a UI to Approve/Deny builds. What I really want from the deployment stuff is to only allow approved builds to advance to the next environment. So only builds marked as approved are an option in the version dropdown for Stage. Right now, however, you can create a whole new release and push it directly to Stage.

Is there some usage pattern I'm missing here? I would expect all the enterprise folks to throw a fit over this, but maybe this is why most people still suggest using regular plans for deployments?

2 answers

2 votes
Ron Chan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 31, 2014

Dustin - join the club https://jira.atlassian.com/browse/BAM-13266

Feel free to voice your displeasure to stimulate some activity on this front.

dustin_barnes April 2, 2014

Yeah... This one seems to wrap up the actual workflow we all want: https://jira.atlassian.com/browse/BAM-13356

0 votes
Ron Chan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 2, 2014

Right you are, that is the over arching one for deployments workflow.

So anxiously waiting for these changes!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events