Certification task assigned to the Managed by group auto-assigns to specific users

[Bobby Campbell]

We've created certification tasks in CMDB Workspace Data Manager and assigned them to the Managed by group field. The intent here is to have the team share the load on completing the certification task, given this particular owner has many hundreds of CIs to certify.  However, the first member of the group that clicks into the task and clicks Review records to certify immediately becomes the Assigned To on the task, and no one else can touch it. 

I might be able to have a group member click Reassign > Assign to me. But in testing that doesn't actually do anything except create a pop-up message: "Are you sure?  Another user is currently reviewing these records. Are you sure you want to reassign this task?" But even after clicking Proceed, the task remains assigned as it was before. So it doesn't seem to work, and if it did, is still not a very friendly way to handle the situation. Does anyone have any experience in this area, that might lead to suggestions for a solution?

[Community Alums]

hi @Bobby Campbell ,

• Instead of assigning a single task to the entire group:

  • Create multiple certification tasks, each for a subset of CIs.

  • Assign each task to a specific user in the group using assignment rules or scripting.

• This ensures proper task ownership and parallel work.

How:

Use Data Manager > Create Certification Task Definitions, and split CI filters per user/team.

Customize Reassignment Logic:

If you're comfortable with customization:

• Modify the client script/UI action logic behind the “Assign to Me” button.

• Ensure it explicitly sets the Assigned To field using GlideRecord and reloads the task.

var gr = new GlideRecord('cmdb_data_cert_task');
if (gr.get(current.sys_id)) {
  gr.assigned_to = gs.getUserID();
  gr.update();
}

[Bobby Campbell]

Thank you @Community Alums . We had two issues:

1) The task being assigned to the first group member to click "Review records to certify" makes sense from an accountability standpoint. It helps ensure that every CI that gets certified has an individual accountable for the action.

2) The "Reassign > Assign to Me" UI action wasn't working due to some issue in our dev instance. Once we completed the upgrade to Yokohama, that issue was no longer present; the UI action is now working as expected.

[Community Alums]

That makes perfect sense — having clear accountability by letting the first person claim the task keeps things traceable and auditable. Glad to hear the “Reassign > Assign to Me” issue was resolved after the upgrade to Yokohama — sometimes these things are just environment quirks!

If you ever want to explore splitting tasks dynamically or making bulk assignment easier, feel free to reach out. Always happy to help brainstorm process improvements or lightweight automation too.