I need to restrict branching to originate from Jira cloud. Meaning, I wish to restrict users from creating new branches without doing so through Jira.
Is there a way to do this?
Hi, @Bill Rachilla!
Thank you for reaching out to Atlassian Community!
Just to confirm that I understand your request correctly: you would like that it was not possible to create branches directly in the Bitbucket repository, only through Jira, is that correct?
If that’s the case, just to make sure we are on the same page, currently, when we create a branch from Jira, we are redirected to Bitbucket to create the new branch:
So, at this time, it is not possible to restrict branch creation only through Jira. What exists is a feature to require issue keys in commit messages (you can enable this by accessing Repository settings > Links), but I believe this is not what you need.
In this case, I would like to ask you for more details about your business case to further understand why this feature would be important to your team. With this information, I can raise a feature request to our dev team.
Thank you. Looking forward to hearing from you.
Kind regards,
Caroline
I'm also looking for this feature ::
I wanted to restrict branch creation without an Isuse type. In other words, A developer cannot create a branch from Bitbucket directly. He/She should create it from the Jira issue only. By this way, i want to prevent some kind of random names been given to Branches
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Prasad Bharadwaj!
We do have a feature request to Restrict branch creation only from Jira:
I would suggest that you add your vote there (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features.
You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
Implementation of new features is done as per our policy here and any updates will be posted in the feature request.
Kind regards,
Caroline
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.