In my project I want to practice a workflow in which the name of a feature branch is strict. For example, if the contributor works on issue #4, he names the branch iss4. So, let's say the desired model is:
What I've done
Branch permissons I've set are shown at the screenshot below:
What I get
So, what I missed? Is it possible to get described workflow?
Thanks for your help,
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs