Please check from the Jira side using ‘Entity Sync Status tab’ in Remote replica payload if it shows ‘label’ because this is how it works for me.
I created ‘field’ as named ‘Request Type’ with type ‘Drop-down’
From Remote replica on Jcloud side it received as:
"labels": [
{
"label": "defect"
},
{
"label": "select_option"
}
]
//(Sample code snippet)
if (firstSync) {
issue.projectKey = "TP"
// Extract all labels as lowercase text
def labels = replica.labels.collect {
it.label?.toLowerCase()
}
// If one of the labels is 'defect', set issue type to Bug
if (labels.contains("defect")) {
issue.typeName = "Bug"
} else {
// Otherwise use mapped type or default to Task
issue.typeName = nodeHelper.getIssueType(replica.type?.name, issue.projectKey)?.name
?: "Task"
}
}
You can completely remove this codeline from:
Jcloud and Zendesk - Outgoing:-
replica.assignee = issue.assignee
Zendesk - Incoming:-
if (!closedStatus.contains(Jirastatus)) {
issue.assignee = nodeHelper.getUserByEmail(replica.assignee?.email)
}
And you also have this snippet that you can remove as you don’t want to sync ‘Assignee’ field in both direction and in any case.
Jira - Incoming:-
// This is to ignore the assignee if the type is Bug or Enhancement
List ignoreAssignee = [“Bug”, “Enhancement”]
if(!ignoreAssignee.contains(issue.typeName)){
// If it’s not a Bug or Enhancement, you can set the assignee from Zendesk
issue.assignee = nodeHelper.getUserByEmail(replica.assignee?.email) // Modify this logic if you want to apply specific assignee rules
}
I don’t find script rule for ‘Priority’ and ‘Severity’ fields. However, here are the relevant docs that can help you configure both the fields.
Please find these helpful thorough docs for how to synchronise and filter the comments between Zendesk and Jira cloud.
Kind regards,
Ashar