Manual Run of Plan Branch causes unexpected behaviors in JIRA Issue View

Summary

If a Plan Branch in Bamboo contains a JIRA Issue Key in its name, a Build from that Branch won't update the JIRA Issue's DevPanel overview if it's not directly linked with the JIRA Issue. Clicking the Build link from the DevPanel however shows this new Build's details.

Steps to reproduce:

1. Create applinks between JIRA and Bamboo
2. From Bamboo, create a new project -> create a new plan (with default job and tasks) -> link the plan with a repository that has a Branch containing a JIRA Issue Key in the Branch name
3. From Plan Configuration -> Branches, manually create a new Plan Branch -> select the Branch with the JIRA issue key in its name -> click Create
   
4. Go to the plan -> branch -> observe that:
   • It's linked with the JIRA issue
   • An initial build has been run successfully (default job and tasks)
     
5. View the JIRA issue and observe that:
   • It's linked with the plan branch with a PASS icon
   • It's not linked with any build
     
6. Configure the plan's default job in a way that the next build will fail e.g. by adding a task ensuring that it will fail
7. Trigger a commit from the linked repository's branch mentioning the JIRA issue key in the commit message
8. Observe the failed build:
   
   This failed build has the JIRA issue directly linked with it thanks to the commit message
9. Observe the failed build in the JIRA issue as well:
   
   Take note that the linked plan branch now displays a WARNING icon
10. Click the Build link from the DevPanel -> observe the failed build:
    
11. Configure the plan's default job again so that the next build will pass
12. Go to the plan -> branch -> manually run the branch -> observe that:
    • The new build is successful
    • It's not linked with any JIRA issue
13. View the JIRA issue and observe that:
    • The DevPanel still shows 1 build failing
    • The plan branch now displays a PASS icon again
      
    • Clicking the Build link from the DevPanel however shows the new successful build:
      

Expected behaviors

• As the new successful build is not linked with the JIRA issue key, clicking the Build link from the DevPanel shouldn't show it. This causes confusion because the DevPanel overview still shows the old failed build (which is expected because the failed build is linked with the JIRA issue)
• On the other hand, if clicking the Build link is expected to show the new successful build (probably because the plan branch itself is linked with the issue), then:
  • This should be clearly documented as an expected behavior
  • The DevPanel overview should display the new successful build as well