SCTASK Assigned To field showing inconsistent behavior

[anil2102]

We are seeing inconsistent behavior in the “Assigned to” field for SCTASK.

- Some group members are not visible in the field
- Group manager (without ITIL role) can be assigned
- In some cases, users without ITIL role and not managers are also selectable

The same assignment works fine in Incidents. Also, the “Assigned to” field is inherited from the Task table for both Incident and SCTASK.

Could you please suggest how to resolve this issue?

Thanks!

[Anupama Singh1 · Accepted solution]

Hi @anil2102 ,

Although Incident and SCTASK both extend the Task table, SCTASK usually has a dictionary override on the Assigned to field. This override changes the reference qualifier, which causes different behavior such as showing non‑ITIL users or missing some group members.

To fix this, check and align the SCTASK dictionary override for assigned_to with the one used on Incident.

Hope this resolves your issue😊 Mark  this correct and close the thread if it helped 👍

[Anand__99]

Hi @anil2102 ,

Verify the dictionary override for Assigned to field. OOB users with 'itil' and 'sn_request_write' roles are available for selection.

If the users have 'sn_request_write' role they will also be available for assignement.

Thanks

Anand