Problem

Currently, a user with administrative privileges cannot edit entities created by another user or agent.

Practical example: a task created by a ChatGPT agent is visible, but the administrator user cannot edit it.

This hinders normal human-agent collaboration: an agent can create tasks, projects, and worklogs, but the system owner/administrator cannot subsequently fix or supplement these records through the standard interface.

What needs to be done

Add administrative permission to edit other users' entities for at least:

• tasks (Task);
• projects (Project);
• worklogs (TaskWorkLog).

Expected behavior

If the current user has administrative privileges (sudo/admin), they must be able to edit the listed entities regardless of who created them or who owns them.

For regular users, current ownership restrictions should remain in place.

What to check

• server-side guards / authorization rules for updateTask;
• server-side guards / authorization rules for updateProject;
• server-side guards / authorization rules for updateTaskWorkLog;
• UI restrictions that might prevent opening the edit form for another user's entity even if allowed on the backend;
• ensure administrative editing does not implicitly change the owner/assignee;
• ensure read access and modification access are checked separately.

Definition of done

An administrator can open and save changes to a task, project, and worklog created by another user or agent, while regular users still do not gain the right to edit other people's data.