Consequences of using the Task_editor role

[tsutherland]

I have a manager who wants to be able to add tasks to a Guided VTB that is using Catalog Tasks. He is currently an itil user and I could give him the role of task_editor to accomplish this, but the description of that role makes me nervous. "Can edit protected task fields"

So I realize that this would allow him to create SCTASKs that are not associated with REQ or RITMs from the service catalog. Is there a problem with doing this that I'm not aware of? He wants to manage his group's work for items that don't have associated catalog items.

[sachin_namjoshi]

This is an old role from the past that allowed a user to edit tasks directly on the task table.

The task_editor role is not directly tied to a license itself. However, it is used by many other roles in order to provide users the ability to edit task records. Instead of creating all of the necessary ACLs under a role, for instance, rm_task_admin, they simply use task_editor to inherit .

I will suggest you to create ACLs to allow manager to manage tasks as per your org requirements.

Regards,

Sachin

[Brian Bouchard]

I don't know about the implications of task_editor role, but my predecessor in our organization accomplished something simlilar by create a "TEAM ABC Service Request" catalog item that could be submitted and added to the team's tasks.  It is a record producer, creating sc_tasks without REQ/RITMs  We haven't had any issues with it since I started in the position a year or so ago.