I need a way to "block" editing and deleting worklogs on a worklog id basis

Richard Vencu

I send my work logs to a third-party system. While they can be edited until a specific event takes place on the backend system, I need a way to block further editing or deleting from Jira after the blocking event.

One way I deduce from the REST API interface is that I can use visibility to let only the admins see the work logs after the event. But it is a bit too harsh for the users, I am curious for other less intrusive ideas.

Richard Vencu

If blocking is impossible, then I need a way to undo the edit or delete action via automation if possible.