-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 11.0.1, 11.0.3
-
Component/s: JIRA integration
-
None
-
1
-
Severity 3 - Minor
Issue Summary
An Internal Server Error occurs when removing a linked Jira issue from a Bamboo Build Run.
Steps to Reproduce
- Initiate a Bamboo build by pushing a change to a Bitbucket repository, ensuring that the commit message references a Jira issue.
- Go to the Issues tab for the resulting build run.
- Try to remove the linked Jira issue from the build.
Reproduced using:
- Bamboo v11.0.1
- JIRA v10.7.3
- Bitbucket v9.6.4
Expected Results
Linked Jira should be removed.
Actual Results
The Delete Action results in the 'Internal Server Page' with the following stack-trace:
java.lang.NullPointerException at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:906) at com.google.common.base.Splitter.split(Splitter.java:385) at com.atlassian.bamboo.plugins.jiraPlugin.actions.EditJiraIssues.splitIssueKeyInput(EditJiraIssues.java:111) at com.atlassian.bamboo.plugins.jiraPlugin.actions.EditJiraIssues.validate(EditJiraIssues.java:87) at com.opensymphony.xwork2.validator.ValidationInterceptor.doBeforeInvocation(ValidationInterceptor.java:250)
The atlassian-bamboo.log reports a 500 exception with the same stack trace:
2025-08-12 14:15:56,800 ERROR [http-nio-8085-exec-32 url: /bamboo/build/removeJiraIssue.action; user: admin] [FiveOhOh] 500 Exception was thrown.
java.lang.NullPointerException: null
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:906) ~[guava-33.2.1-jre.jar:?]
at com.google.common.base.Splitter.split(Splitter.java:385) ~[guava-33.2.1-jre.jar:?]
at com.atlassian.bamboo.plugins.jiraPlugin.actions.EditJiraIssues.splitIssueKeyInput(EditJiraIssues.java:111) ~[atlassian-bamboo-web-11.0.1.jar:?]
at com.atlassian.bamboo.plugins.jiraPlugin.actions.EditJiraIssues.validate(EditJiraIssues.java:87) ~[atlassian-bamboo-web-11.0.1.jar:?]
at com.opensymphony.xwork2.validator.ValidationInterceptor.doBeforeInvocation(ValidationInterceptor.java:250) ~[struts2-core-6.7.3-atlassian-1.jar:6.7.3-atlassian-1]
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Loading...