When a Bitbucket project has a project-level Jira application link, opening a Jira issue link from that project's commits, commit messages still asks the user to authenticate against the global primary Jira application link first. Only after that is the user redirected to the issue in the project-level Jira instance.

Users without an account on the global primary Jira can't complete this step, so they can't open the issue from Bitbucket in a new tab. This happens even though they have access to the issue in the project-level Jira, and the issue details pop-up in Bitbucket shows it correctly.

Bitbucket should authenticate and redirect using the project-level Jira application link when one is configured, and fall back to the global primary link only when there isn't one. 
This is related to BSERV-20380. That ticket asks for an option to skip authentication against the primary link.