You have a ticket which is not assigned to a processor for now, which means the "Assign To" field is blank.
Now if logon user edits the Ticket and change some particular fields, such as 'Incident Category' or 'Customer' or add notes, the incident will be assigned to the logon user automatically.
SAP Cloud for Customer
Reproducing the Issue
Go to Service work center.
Go to Tickets work center view.
Pick one ticket which is not assigned yet.
Edit the ticket, change the 'Incident Category' or change the Customer, or add a note, etc.
You find the ticket is assigned to you automatically. (The 'Assign To' field is flagged with your name)
In Business Configuration, for the activity "Tickets for Customer Support" or "Tickets for Employee Support", you have maintained the party determination for the Processor as "Current User".
Go to Business Configuration work center.
Find the Activity: Tickets for Customer Support or Tickets for Employee Support.
Open the activity and click "Maintain Involved Parties".
Select Processor and click "Maintain Determination".
- Here, you can see you only checked the one "Current User".
So this is the standard behavior when you configured the party determination for processor as above.
The "Current User" determination will not only be triggerred for the initial ticket creation, but will also be triggered when someone edit the particular fields if the ticket is not assigned for now.
OBS: This behavior is true for Tickets with Source = Manual Data Entry and Source = Phone Call. This can be enabled for emails upon request. Please raise an incident to SAP Support if you'd like this for emails.
Ticket, Logon User, Current User, Assign to, Processor, Assigned To User , KBA , LOD-CRM-SRP , Service Request Processing , LOD-CRM-PM-SRV , C4C Product Management - Service , How To