Summary

Users are forced to authenticate to the 'primary' application when there are multiple application links of the same type using OAuth. If Bamboo is linked to multiple Jira instances, users that exist in one Jira instance does not necessarily exist in others. However Bamboo is forcing users to authenticate to the Jira instance marked as the 'primary' application when looking at the build result summary page even if the links are not pointing to that Jira instance, and there's no way to bypass the first prompt for authentication to get to the second one, for the correct Jira instance.

Users must first authenticate to the Jira instance marked as the 'primary' application so then they can authenticate to the second Jira instance and retrieve the links.

Steps to Reproduce

1. Create an application link between Bamboo and two different Jira instances.
   • In this example, I have linked Bamboo to Jira 7.5.0 (primary) and Jira 7.3.1.
     
2. Access a build result summary page and a) create a link to one or more existing Jira issues inside 7.3.1 or b) create one or more issues from inside Bamboo to Jira 7.3.1 using the Actions > Create issue link.
3. Create a new user inside Bamboo and Jira 7.3.1 (e.g. test-user).
   • The user will have access to Bamboo and Jira 7.3.1 to work with that plan and issues that are linked to that build.
4. Access Bamboo as test-user and visit the build result summary page for that build. The one we just created a link to a Jira 7.3.1 issue in step 2.
5. Keep in mind that the issue only exists in Jira 7.3.1 as well as the test-user.

Expected Results

Bamboo will prompt the user to authenticate in both Jira instances or at least provide a mechanism so the user can choose with application he needs to authenticate.

Actual Results

1. Bamboo prompts the user to authenticate in Jira 7.5.0 even though that build is not linked to any issues inside Jira 7.5.0.
   
2. In this case, if I create the test-user inside Jira 7.5.0, I can authenticate and get to the second authentication prompt, for Jira 7.3.1:
   
3. The user is able to retrieve the links to the Jira issues as well as the statuses after that:
   

If the user does not hold an account in the 'primary' application, the user is not able to get past the authentication prompt and therefore unable to load Jira issues inside Bamboo.