We really have no way to hook up Jira to our Bitbucket without this feature since smart commits are on by default and our entire workspace's projects are defaulted into the repo list. This ends up being 500+ for my organization and we cannot uncheck all the smart commit options in time.

Not being able to hook up Jira is breaking our audit logs that tie our Jira tickets directly to our Bitbucket commitments.

We had this set up prior in our old Jira Server setup but the cloud migration we have recently performed has made it so we need this to be reconfigured, yet there is no reasonable way to do this.

When you have multiple teams and multiple project within the same organization, It's impossible to work with this limitation.
Really disappointed that is not addressed after so long time.

Agreed with all the other commentors, this is a huge issue and a blocker to us using the GitHub integration. I see there is also a thread of people discussing the same issue on the GH repo for the GitHub integration: Jira projects limit access to Github organization · Issue #1233 · atlassian/github-for-Jira

This is also what lead to our current support ticket JST-894604

 This is really needed, sometimes I have developers working in some project that shouldn't know about or care about other repos in my GitHub organization. Given that some sensitive repos need a certain security clearance to access. 

Right now am forced to share the whole organisation repos which is a security issue.

+1 to Nick Hammonds suggestion about mapping repositories to components. That would be very useful and make it a lot less error prone.

+1. This is very much needed.

Project links are not the solution.

Need something that will help to map Jira projects with Bitbucket repositories. Current DVCS integration with a Bitbucket instance, opens up the link to all Jira projects who might end up creating branches at unexpected locations.

Came looking for exactly the same thing - massive agreement that this would be a big usability plus for us, too.

Furthermore, it would be incredibly useful to have a 'component' map over to a Bitbucket repository, so when a user clicks 'create branch' in Jira, the correct repository is already selected for them in the box that appears. 

We have +20 repos and finding the correct one in the list when branching is very painful, and mistakes are often made. If we could map a default repository to a component that would be absolutely great.

Being able to link specific components to repositories would be massively usable.  So i have a component called 'user-api', the repo would be bibucket.org/username/user-api.  So when creating a new branch, the repo is selected already.