This problem analyzer helps resolve issues encountered while trying to deploy Custom site, Dashboard, ReportFolder, WorkflowAlert, Queue, Custom field or Approval process metadata types that have different referenced users between the source and target environments.
What triggers this problem analyzer?
If your deployment package contains a metadata that has new or changed reference users, you'll see a message in Gearset like: "If a changed queue (or metadata type) references a user that does not exist in the target org, it will cause the deployment to fail.".
What problem is it solving?
Usernames are unique to each org, therefore it isn't possible to deploy referenced user from a source to target's existing item that has new or changed user in the target. Attempting to do this will cause your deployment to fail with a Salesforce error "Cannot find a user that matches any of the following usernames".
How does it work?
Gearset will identify any metadata item with a referenced user in your deployment package that seems to have been created or changed (when compared to the target environment).
Gearset will fix the deployment by replacing any new or changed referenced user with the referenced user named in the target org's metadata item.
