"Assigned to" user does not belong to the Assignment group in the incident recordDescription Assignment Group and Assigned to are not in sync on some Incidents "Assigned to" user not belong to assignment group in incident record If incidents are being created through filter "incident assigned to me" & if there is some default value set in the assignment group, then this issue can occur. Step to reproduce in out-of-the-box (OOB) instance: In the assignment group set some default value Impersonate any user who does not belong to that group Use filter "incident assigned to me" Click on new, assigned to will be populated with that username though the user is not part of that group CauseLogged in username is getting passed in URL parameter when the user is using:"assigned to me " option while creating the incident.ResolutionApply one of the following approaches: Write a display business rule which will check logged in user is part of the current assignment group or not, if not then it will clear the 'assigned to' valueCreate an onLoad client script which will call script include. In the script, write logic to check group membership. If the logged in user is not part of the assignment group then clear the value