Error: Request type requires a custom field but none was set through exalate config

General Questions
, ,
1

Originally asked by ben friedman on 19 October 2020 (original question)

Hi,
to sync comments between JSD and ZD, i want to set the request type on the JSD (cloud) side.
on the incoming (jsd) side -

issue.typeName     = nodeHelper.getIssueType(replica.typeName)?.name ?: "EasyShip issue"

issue.customFields."Request Type".value = "EasyShip request"

in the local (jsd) replica, the issue type is set correctly.
i didnt see the request type field appearing in the replica.
i confirm that both names (EasyShip issue, EasyShip request) are correct.

more over, i tried syncing another issue (without comments now).
on the JSD, im getting the error -

Request type `EasyShip request` requires a custom field 10049 of type `com.atlassian.jira.plugin.system.customfieldtypes:select` but none was set through exalate config.

So i guess the request type is not a custom field? in the exalate documentation its suggested that the request type is a custom field…

2

Answer by Juan Grases on 19 October 2020

Hi!

The last error indicates that there a custom field that is required when creating a EasyShip request. Could you check which custom field is that (id is 10049) and make sure you set it on your incoming processor?

Best regards,
Juan

Comments:

ben friedman commented on 19 October 2020

i’ve set all the mandatory fields for the request, before setting the request type. this resolved the issue.

3

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.