Assign to Me" action does not populate Assignment Group – OOTB behaviour or configuration option?

[Community Alums]

Hello ServiceNow Community,

I am currently validating an out-of-the-box (Zurich) Incident Management implementation and noticed the following behaviour.

When an analyst uses the"Assign to Me" action from Agent Workspace:

• Assigned To is correctly populated with the logged-in user.
• Assignment Group remains blank.
• If Assignment Group is mandatory, the record cannot be saved until the agent manually selects a group.

The explanation provided by our implementation partner is that a user may belong to multiple groups, therefore ServiceNow cannot automatically determine which Assignment Group should be selected.

While this explanation makes sense, I was under the impression that some ServiceNow implementations use a default assignment group concept (either OOTB) to streamline the assignment process.

My questions are:

1. Is it expected OOTB behaviour in ServiceNow Zurich that the"Assign to Me" action only populates Assigned To and never Assignment Group?
2. Does ServiceNow provide any OOTB mechanism to identify a user's preferred or default assignment group?
3. Are organizations typically implementing a custom field (for example, a "Default Group" on the user record) and using a Business Rule / Client Script to populate Assignment Group automatically?
4. What is considered the recommended practice to avoid forcing analysts to manually select their group every time they use Assign to Me?

I am trying to determine whether the observed behaviour is:

• Standard OOTB behaviour,
• A configuration choice,
• Or a missed optimization opportunity.

Thank you in advance for your feedback and experience.
Daniel

[pavani_paluri · Accepted solution]

Hi @Community Alums ,

What you're seeing is actually what I would expect from an OOTB Zurich implementation.

The Assign to Me action is intended to populate the Assigned To field with the current user. It doesn't automatically set the Assignment Group, and the reason your implementation partner gave is generally the same rationale ServiceNow follows: many analysts belong to multiple groups, so the platform has no reliable way of knowing which group should be chosen automatically.

As far as I'm aware, there isn't an OOTB concept of a user's default assignment group that is automatically used by Incident Management when an analyst clicks Assign to Me. The platform leaves that decision to the organization's process and configuration.

In practice, I've seen three common approaches:

• Leave the OOTB behavior as-is and require the analyst to select the appropriate group.
• Add a custom Default Assignment Group field on the user record and populate Assignment Group automatically when the analyst assigns the record to themselves.
• Customize the Assign to Me action so that it sets both Assigned To and Assignment Group based on predefined logic.

Personally, I would classify your observation as:

• Standard OOTB behavior
• A deliberate design choice to avoid ambiguity when users belong to multiple groups.
• A potential usability improvement opportunity if most analysts primarily work from a single support group

So, I wouldn't consider this a defect or misconfiguration. However, if analysts repeatedly select the same group every time they use Assign to Me, implementing a default-group mechanism is a common and worthwhile optimization.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P