A wrong user was assigned then un-assigned, but the error is not going away

General Questions
, ,
1

Originally asked by Exalate user on 16 September 2020 (original question)

The sync breaks even though this wrong user no longer exists. Initially, this user was not part of the project, this is where the error came from.

2

Answer by André Leroy-Beaulieu Castro on 17 September 2020

Hi Irina,

To give a bit more context, your original error was:

Could not update issue `10,104`: Field assignee: User 'alex' cannot be assigned issues..

and to make sure this doesn’t happen, you can add this logic to your Incoming processor:

def remoteAssignee = nodeHelper.getUserByEmail(replica.assignee?.email)
if (nodeHelper.isUserAssignable(issue.projectKey, remoteAssignee)) {
  issue.assignee = remoteAssignee
} else {
  issue.assignee = null 
}

This will make sure the assignee is set only if it’s assignable in the destination project, if it isn’t it will stay unassigned.

Thanks,

André

3

Answer by Francis Martens (Exalate) on 17 September 2020

Hi Exalate user

Can you provide some more details.

  • What are you trying to implement
  • What is your outgoing and incoming sync processor (or are you using a visual connection)
  • What is the error you encounter