We are working with an outside vendor that has requested to use their Jira instance and our bitbucket.
They are requesting we give them an oauth token for dvcs connector, but it seems like their JIRA will be able to access all our repos.
Is there a way to connect a second jira instance to bitbucket and restrict its access to a particular repository?
Hey @Matthew Meineke,
No, DVCS connector is an account-level add-on in Bitbucket, so its permissions cannot be restricted to a particular repository.
What I can think of as a workaround is creating another account, forking the repository in question into that account and then keeping syncing that fork with the upstream (this is manual though). Not sure if there're other ways to set up what you're trying to achieve.
Cheers,
Daniil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.