-
Bug
-
Resolution: Fixed
-
Highest
-
4.19.0, 4.13.10, 4.18.2
-
None
-
28
-
Severity 2 - Major
-
1,124
-
Issue Summary
When we move an issue from one Issuetype to another, the below error is thrown if the Request participant field is filled in. If there is no Request participants fields, the move is successful.
Steps to Reproduce
- Create a service management project
- Create an issue and add Request participant
- Try to move the issue to another issuetype
Expected Results
- Issue is moved successfully
Actual Results
- The below error is thrown >
The below exception is thrown in the atlassian-jira.log file:
2021-08-25 14:30:19,483+0530 http-nio-41310-exec-11 ERROR [o.a.c.c.C.[.[localhost].[/j81310].[action]] Servlet.service() for servlet [action] in context with path [/j81310] threw exception [java.lang.NullPointerException] with root cause java.lang.NullPointerException at com.atlassian.servicedesk.internal.customfields.participants.ParticipantsCFType.getProject(ParticipantsCFType.java:328) at com.atlassian.servicedesk.internal.customfields.participants.ParticipantsCFType.validateFromParams(ParticipantsCFType.java:290) at com.atlassian.jira.issue.fields.ImmutableCustomField.needsMove(ImmutableCustomField.java:1103) at com.atlassian.jira.web.action.issue.MoveIssueUpdateFields.doDefault(MoveIssueUpdateFields.java:73) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) ... 2 filtered at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) ... 7 filtered
Workaround
The only workaround is to remove the Participants, move the issue and re-add the participants.
A simple option to perform this is to configure an automation rule to remove request participants on issue creation and add a comment with the names of participants which can then be added back after moving the issue.
[JSDSERVER-8661] Moving an issue from one issue type to another throws NullpointerException if the Request participants field is filled in
bump +1,
Is there a fix for this yet ? couldn't find version 8.19.2 when we tried to test it via "Plan your upgrade", versions went up until 8.19.1..
I agree with Morten, would be great if this was added to an 8.18.x release. Would require much less testing for our team so we could just do a quick patch, rather than jumping to the next version and full test scripts run.
It's not because it's marked as not compatible that it is... I'm running with incompatible plugins, it still works well... Test it before your go live.
This is actually annoying........We've upgrade to 8.18.2 when all our addons was compatible.
Now we hit this bug, which only is bugfix released for 8.19.2 going live yesterday (And 8.19.x is still quite new).
And now we end up between a rock and a hard place........... We cannot upgrade to 8.19.2........14 addons not yet compatible!
This bugfix could have been released for 8.18.x versions as well as we have no way of knowing, when we get 3 party vendor compability.
We encountered this bug as well with significant impact to how we receive new requests in Jira. We developed a workaround with Automation to:
- Remove Participants when a request is created.
- Add a comment to the issue with the participant names.
- A user can move the issue to a new issue type as they please and then add the participants back to the issue manually.
Looking forward to the fix in the next release, but it is definitely time consuming to upgrade for one bug fix.
https://getsupport.atlassian.com/browse/SDS-61181