We have a stash project for each JIRA project.
Both projects have app links (https://confluence.atlassian.com/display/JIRA060/Adding+Project+Links+between+Applications)
I suppose when I go to some JIRA issue and click on "create branch" I should be suggested to create a branch in the proper stash project (set on project link), but JIRA always direct me to the last stash project where I have created my last branch.
because of that, some users have created branches in wrong stash projects.
How can I avoid that?
Is it possible to restrict to create branches in a wrong project?
There is an issue for this already: https://jira.atlassian.com/browse/JRA-39322.
Until this is naively supported by Stash, you could try our new (and free) Stash add-on Create Branch Repository Selector which selects the Stash repository for the JIRA project in the create branch dialog when coming from JIRA. The mapping between a JIRA project and a Stash repository is implemented by scanning the commit messages for JIRA issue keys. It takes the repository which has been tagged the most with JIRA issue key's for the JIRA project the user would like to create a branch for.
Hope this helps.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot