These lines of config should do the trick. Please try them out. Keep in mind that you have to change the issue.projectKey value and also add the correct issue types in the mapping.
//map issue types between source and destination instances.
def issueTypeMapping = [
// "remote issue type" : "local issue type"
"Task" : "Task",
"Issue" : "Story"
]
if (firstSync) {
issue.projectKey = "EXADEMO"
// Set type name from source issue, if not found set a default
issue.typeName = issueTypeMapping[replica.type?.name] ?: "Story"
} else {
def localIssueType = issueTypeMapping[replica.type?.name]
if (localIssueType) {
issue.type = nodeHelper.getIssueType(localIssueType, issue.project?.key)
}
}
Always take into account that the incoming script on the Jira side is responsible for applying changes, and this can be done independently from what happens on the other side.
so changing issue information can always be done based on an incoming sync
Both fields - issue type and request type can be changed, but there are conditions imposed by the tracker.
You can either try and see, or check the documentation.
Hello,
We would like to know if this plugin supports changing the Issue Type in Jira after changing the Work Item type" in Azure DevOps.
We work with 2 Levels of support: A 1st Level in Jira Cloud (Jira Service Management) where the customers rise their issues/requests and a 2nd Level in Azure DevOps where the developers decide whether it's an issue or a request by changing the work item type and solve the task.
Right now we have 3 different issue types in Jira with different workflows and SLAs and with a sync plugin it creates a workitem in Azure DevOps with the same features, but if someone changes the work item type in Azure DevOps the Issue Type won't change in Jira and we would like to know if Exalate could do that.
Would it also be able to change the field Request Type in Jira?
Thanks for your help.
Regards,
Alma