JIRA fails to retrieve Plan Branches from Non-Primary Bamboo

Summary

If JIRA is linked with more than 1 Bamboo instance and an issue has links to Plan Branches from multiple Bamboo, JIRA is only able to retrieve and display the link from the Primary Bamboo.

Steps to reproduce

1. Create applinks between JIRA and 2 different Bamboo instances
2. Create a Plan Branch in each Bamboo instance that is linked to a single JIRA issue
3. View the JIRA issue's Issue Links section

Expected behavior

JIRA is able to retrieve and display the 2 links properly.

Actual behavior

JIRA is only able to retrieve and display the link from the Primary Bamboo. It fails to load the link from the Non-Primary one:

From JIRA log, the following message is seen:

2017-07-22 19:54:15,471 http-nio-8740-exec-3 WARN admin 1194x2257x1 1hycggs 10.60.2.10 /rest/viewIssue/1/remoteIssueLink/render/10001 [c.a.j.p.e.bamboo.view.BuildLinkRenderer] Error when fetching Bamboo Plan status for key BAM-SUB1 [Project BAM not found.]

Notes

1. The URLs of the links are correct. This means, users can actually click the "Failed to load" link to go to the respective Plan Branch (probably the only known Workaround).
2. JIRA however seems to use the Base URL of the Primary Bamboo to retrieve all the links' information, leading to 404 Not Found (Failed to load).

Diagnosis

Turning on Debugging for org.apache.http.wire, the following log is captured:

• For link from Primary Bamboo:

2017-07-22 20:08:33,962 http-nio-8740-exec-12 DEBUG admin 1208x2436x2 1hycggs 10.60.2.10 /rest/viewIssue/1/remoteIssueLink/render/10002 [o.apache.http.wire] http-outgoing-174 >> "Host: 192.168.1.100:9003[\r][\n]"
...
2017-07-22 20:08:33,992 http-nio-8740-exec-12 DEBUG admin 1208x2436x2 1hycggs 10.60.2.10 /rest/viewIssue/1/remoteIssueLink/render/10002 [o.apache.http.wire] http-outgoing-174 << "HTTP/1.1 200 OK[\r][\n]"

• For link from Non-Primary Bamboo:

2017-07-22 20:08:33,964 http-nio-8740-exec-14 DEBUG admin 1208x2435x1 1hycggs 10.60.2.10 /rest/viewIssue/1/remoteIssueLink/render/10001 [o.apache.http.wire] http-outgoing-175 >> "Host: 192.168.1.100:9003[\r][\n]"
...
2017-07-22 20:08:34,014 http-nio-8740-exec-14 DEBUG admin 1208x2435x1 1hycggs 10.60.2.10 /rest/viewIssue/1/remoteIssueLink/render/10001 [o.apache.http.wire] http-outgoing-175 << "HTTP/1.1 404 Not Found[\r][\n]"

 Apparently, JIRA uses the same URL (192.168.1.100:9003) to retrieve the links.