Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-8661

Moving an issue from one issue type to another throws NullpointerException if the Request participants field is filled in

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 4.20.0, 4.13.11, 4.19.1
    • 4.19.0, 4.13.10, 4.18.2
    • Issue View
    • None

      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

      1. Create a service management project
      2. Create an issue and add Request participant
      3. 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.

        1. Screenshot 2021-08-25 at 2.29.21 PM.png
          Screenshot 2021-08-25 at 2.29.21 PM.png
          415 kB

            [JSDSERVER-8661] Moving an issue from one issue type to another throws NullpointerException if the Request participants field is filled in

            Rob made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 662582 ]
            Alex Cooksey made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 659308 ]
            KellyW (Inactive) made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 601916 ]
            Ryan Brailey made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 601916 ]

            Loc Nguyen (Inactive) added a comment -

            https://getsupport.atlassian.com/browse/SDS-61181

            Loc Nguyen (Inactive) added a comment - https://getsupport.atlassian.com/browse/SDS-61181

            Krystian Tabak added a comment -

            +1

            Krystian Tabak added a comment - +1
            Rodrigo Rosa made changes -
            Fix Version/s New: 4.20.0 [ 96191 ]

            Jh added a comment -

            8.20 just released but I did not see this issue in the "Issues Resolved" list?

            Jh added a comment - 8.20 just released but I did not see this issue in the "Issues Resolved" list?

            Geeta Basker added a comment -

            We're seeing this issue in version 8.18.2 again.

            Geeta Basker added a comment - We're seeing this issue in version 8.18.2 again.

            Michel Azzam added a comment -

             Bump +1,

            Can't find version 8.19.2 ...

            Michel Azzam added a comment -  Bump +1, Can't find version 8.19.2 ...

              jxu2@atlassian.com Sam Xu
              sthottamkara@atlassian.com Sandhya Thottamkara
              Affected customers:
              31 This affects my team
              Watchers:
              77 Start watching this issue

                Created:
                Updated:
                Resolved: