My company uses Jira cloud, Confluence cloud, and BitBucket cloud. We were recently acquired by a larger company that also uses Jira cloud and Confluence cloud.
We've managed to link BitBucket to the larger company's Jira via the DVCS accounts page. What's the easiest way to seamlessly allow users in the new company's Jira to access our BitBucket repos via the "Create branch" link in Jira issues?
Mike
Hi Mike,
In order for a user to be able to create a branch in a repo (either via the "Create branch" link in Jira issues, or from Bitbucket website), they will need to have at least write access to this repo.
So, if you want to allow those users to create branches in your repos, you'll need to give them at least write access.
You can invite those users directly to specific repos, by adding their email from the Repository settings page > User and group access > section Users.
Alternatively, you can add those users to an existing User group of your workspace, or create an extra User group in the workspace for these users, and add their emails in the user group. Then, add this User group to the repo(s) you want it to have access to from the Repository settings page > User and group access > section Groups.
If you don't want them to automatically gain access to newly created workspace repos, make sure to set in the User group Default repository access: None.
In both cases, users will need to first accept the email invitation they'll receive in order to get access.
If you have any questions, please feel free to let me know.
Kind regards,
Theodora
Thanks for the response Theodora. One thing I forgot to mention is that the developers have an email address from the old company that they've been using with BitBucket, and now also have an email address for the new company, which they use for accessing the new company's Jira. What we'd like is some way to merge access for the two email addresses so we maintain all the history for the single developer. We can add folks into BitBucket using their "new" email address, but then the history for that person will diverge. Does that make sense?
Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike,
Thanks for the clarification, yes, that makes sense. (I misunderstood the issue, I thought that you wanted to add users from the new company in Bitbucket.)
Just to make sure, would you like developers to have their new email address as the primary one in Bitbucket?
If this is the case, this is something that can be achieved with the help of Bitbucket Cloud support team only.
The reason for that is that there are two Atlassian accounts for each user now, one with the old email and one with the new one. We use Atlassian accounts (the ones for https://id.atlassian.com/) for authentication to both Bitbucket Cloud and JIRA Cloud.
If there is an Atlassian account for both the old and new email already, users cannot make the email change themselves, but Bitbucket Cloud support team can assist with this.
I would suggest that you open a support ticket and mention:
- the exact same thing you told me in your previous reply
- the domain of the old and new emails
- confirm also if you want the developers to have the new email as primary one of their Bitbucket account
- provide a list of the Bitbucket users
and the engineer working on your case will provide further guidance and assistance.
You can open a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with" select "Technical issues and bugs" and then Bitbucket Cloud as product.
Please feel free to let me know if you have any questions.
Kind regards,
Theodora
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.