Summary

There is an open bug;

Users are forced to authenticate to the 'primary' application when there are multiple application links of the same type

 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.

Request

A feature where Bamboo first checks for a Jira Issue key from the Project-level Application Link, and only if none is found should Bamboo check the Global-level Application link. This means Bamboo will honor the Project-level application links which it does not currently.

This feature will help in a situation where user permission is such that Bamboo users may only have permission to some Jira instances, and those instances can be added to the respective Project-level application link.

With this, Bamboo admin will only need to include the application link for instances users or group has permission to as Project-level application link.

Presently Project-level Application link feature exists at Jira side, where Jira project can be linked to Bamboo project and then Release panel shows plans from that Bamboo project.