Behaviour of UI Action "Assign to me" for incident records is different for Task and Incident tables - Support and Troubleshooting

Behaviour of UI Action "Assign to me" for incident records is different for Task and Incident tables Summary Behaviour of 'Assign to me' UI action on Incident table: Incidents can be reassigned only if the user is member of the same assignment group of that in incident record. It is not allowed in case user is from a different group.

Behaviour of 'Assign to me' UI action on Task table for incident records: Incidents can be reassigned even if the user is not part of the assignment group.

Reason for this change in Behaviour:

The task table is a parent table for many tables like incident, problem, change, incident_task, change_task, sc_task, sc_req_item, kb_feedback_task, etc. So the "Assign to me" UI action on "task" table (sys_ui_action.do?sys_id=4c1cfa36c611227501e6728036d9723b) is applicable to all the child tables of task table. For Incident table, the "Assigned to" field is dependent on "Assignment group" and hence validation/condition should be performed to check whether the "assigned_to" user is member of "assignment group". For this reason, there is a separate UI action - 'Assign to me' (sys_id:3b991ad673da20103e366238edf6a7f3) for Incident table which enforces the required validation. On other tables like kb_feedback_task, there is no such dependency due to dictionary override - sys_dictionary_override.do?sys_id=52bb223167b30300d358bb2d07415abc. Hence enforcing validation/condition in the UI action for the task table to check for the dependency is not appropriate.