You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server Info (please complete the following information):
OS: Ubuntu 20.04.6 LTS
Browser: ANY
RMM Version v0.20.0:
Installation Method:
Standard
Standard with --insecure flag at install
Docker
Agent Info (please complete the following information):
Agent version (as shown in the 'Summary' tab of the agent from web UI): ANY
Agent OS: ANY
Describe the bug
When right-clicking on any task in the Tasks tab and and selecting "Run task now", the History only shows "Initiated by: system" instead of the user who forcefully ran the task.
To Reproduce
Steps to reproduce the behavior:
Go to any agent with a task
Click on Tasks
Right-click on any task
Select "Run task now"
Click on "History" and see the column "Initiated by" as "system"
Expected behavior
The user who runs the task should be deemed the initiator in the task history logs. This would be best practice for user auditing to confirm who ran which commands, vs, what was automatically triggered by a schedule. Scheduled tasks would of course remain initiated by "system".
Screenshots
User action:
Current incorrect result:
Additional context
The text was updated successfully, but these errors were encountered:
Server Info (please complete the following information):
Installation Method:
--insecure
flag at installAgent Info (please complete the following information):
Describe the bug
When right-clicking on any task in the Tasks tab and and selecting "Run task now", the History only shows "Initiated by: system" instead of the user who forcefully ran the task.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The user who runs the task should be deemed the initiator in the task history logs. This would be best practice for user auditing to confirm who ran which commands, vs, what was automatically triggered by a schedule. Scheduled tasks would of course remain initiated by "system".
Screenshots
User action:
Current incorrect result:
Additional context
The text was updated successfully, but these errors were encountered: