Actions
User Story #303
open
Epic #49: Implement user, groups and permissions management
Feature #273: Module identity
As an administrator, I want to see when a module acted on its own, so that automated changes are not attributed to nobody
User Story #303:
As an administrator, I want to see when a module acted on its own, so that automated changes are not attributed to nobody
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Modules do things nobody asked for at that moment — scheduled restarts, cleanups, retries. Recorded history should say which module did it.
Acceptance criteria
- Each module has an identity that appears as the actor on what it does on its own initiative
- Work a module does on someone's behalf is attributed to that person, noting which module carried it out
- A module's identity is not something access can be given to
- The identity disappears with the module when it is uninstalled
Rejection reason
Superseded by the rewritten epic #49
Updated by
Actions