-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
0
-
1
-
Summary
Right now Bamboo stores the Jira issue key associated to a build result in the BRS_LINKEDJIRAISSUES table. The problem is with the way we store the information. Bamboo does not keep the entire URL to the Jira instance where the link was originally pointing to (e.g. http://localhost:8080/browse/TEST-1), only the Jira issue key (e.g. TEST-1). Therefore, if you have multiple Jira instances connected to Bamboo and the prefix of a Jira issue exists in more than one Jira instance, Bamboo will always assume that the Jira issue is coming from the 'primary' application link or in case there's no Jira issue with that prefix in the 'primary' application, the first Jira application that has a matching prefix, following top to bottom in the list of application links.
Expected Results
We should improve the way we store this information so that when we first create a link between a Jira issue and a build result, the entire URL to the Jira issue is stored (e.g. http://localhost:8080/browse/TEST-1 instead of just TEST-1) to avoid confusion and preserve the original association.
Hi everyone,
Thank you for your interest in this issue.
We believe that this functionality works as expected. The information that Bamboo parses from commit comments contains only key to the JIRA issue. How is it resolved to URL is a matter of what Jira instances are connected to Bamboo at the moment of resolution. We decided not to store the whole URL for the simple fact that customers might want to migrate their Jira instances in which case we'd end up with a bunch of dead links.
We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.
To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
Bamboo Team