Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


Problem

Customers are unable to add participants to a Service Desk request. 

  • Click "Add People" in the Service Desk request
  • Look up the user that needs to get added as participant
  • Once found, click "Add" to add the participant

After the "Add" button has been clicked, nothing happens.

The following appears in the atlassian-jira.log

http-bio-8080-exec-36 ERROR <user> 646x217666x1 5hs9lj <IP>,<IP> /rest/servicedesk/1/servicedesk/customer/participant/addparticipants/<Issue-ID> [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: com.atlassian.jira.issue.customfields.impl.FieldValidationException: Boolean parse error: null
com.atlassian.jira.exception.DataAccessException: com.atlassian.jira.issue.customfields.impl.FieldValidationException: Boolean parse error: null

Followed by a:

Caused by: com.atlassian.jira.issue.customfields.impl.FieldValidationException: Boolean parse error: null
	at com.xiplink.jira.jql.GitCommitsReferencedCF.getSingularObjectFromString(GitCommitsReferencedCF.java:44)
	at com.xiplink.jira.jql.GitCommitsReferencedCF.getSingularObjectFromString(GitCommitsReferencedCF.java:20)
	at com.atlassian.jira.issue.customfields.impl.CalculatedCFType.getValueFromCustomFieldParams(CalculatedCFType.java:76)
	at com.atlassian.jira.issue.fields.CustomFieldImpl.updateIssue(CustomFieldImpl.java:1264)

This only appears to happen for Customer user types in JIRA Service Desk.
Agents do not appear to be impacted by this. 

Cause

This issue is caused by the GIT Integration Plugin for JIRA of version 2.6.9
Version 2.6.10 provides a fix for this issue.

Workaround

Downgrading the add-on to version 2.6.8 will prevent this issue from happening.
In addition, 2.6.10 and newer versions provide a fix as well.

Help us improve!