[GH-ISSUE #1096] Different times being shown in Automation Manager #673

Closed
opened 2026-03-02 02:18:11 +03:00 by kerem · 1 comment
Owner

Originally created by @subzdev on GitHub (Apr 25, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1096

Originally assigned to: @sadnub on GitHub.

Server Info (please complete the following information):

  • OS: Ubuntu 20.04
  • Browser: Any
  • RMM Version (as shown in top left of web UI): 0.13.3

Installation Method:

  • [ x] Standard
  • Docker

Agent Info (please complete the following information):

  • Agent version (as shown in the 'Summary' tab of the agent from web UI): Latest
  • Agent OS: Windows 10

Describe the bug
When editing a task script from an automation policy, the time (not month/year date) is different than what it shows in the table. Looks like it is 7 hours off, so if a script is set to run at 5PM, it would show 10AM in the edit screen.

To Reproduce
Steps to reproduce the behavior:

  1. Create a task script in an Automation policy
  2. Edit that task script
  3. Times will be different when compared to the task script table for the automation policy and when editing it

Expected behavior
Times should be consistent

Originally created by @subzdev on GitHub (Apr 25, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1096 Originally assigned to: @sadnub on GitHub. **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: Any - RMM Version (as shown in top left of web UI): 0.13.3 **Installation Method:** - [ x] Standard - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): Latest - Agent OS: Windows 10 **Describe the bug** When editing a task script from an automation policy, the time (not month/year date) is different than what it shows in the table. Looks like it is 7 hours off, so if a script is set to run at 5PM, it would show 10AM in the edit screen. **To Reproduce** Steps to reproduce the behavior: 1. Create a task script in an Automation policy 2. Edit that task script 3. Times will be different when compared to the task script table for the automation policy and when editing it **Expected behavior** Times should be consistent
kerem 2026-03-02 02:18:11 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@sadnub commented on GitHub (Apr 25, 2022):

This will be fixed in the next release. Thanks!

<!-- gh-comment-id:1108914882 --> @sadnub commented on GitHub (Apr 25, 2022): This will be fixed in the next release. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#673
No description provided.