Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incomplete output in section "Effective Patch Policy" #1982

Open
1 of 3 tasks
janstalhut opened this issue Aug 15, 2024 · 0 comments
Open
1 of 3 tasks

Incomplete output in section "Effective Patch Policy" #1982

janstalhut opened this issue Aug 15, 2024 · 0 comments

Comments

@janstalhut
Copy link

Server Info (please complete the following information):

  • OS: Debian 12
  • Browser: Firefox
  • RMM Version (as shown in top left of web UI): 0.19.3

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): 2.8.0
  • Agent OS: [e.g. Win 10 v2004, Server 2016] Windows 10/11/2016/2019/2022

Describe the bug
In the edit dialog of an agent, in the "Automation Policies" tab, in the "Effective Patch Policy" section, there is incomplete information about the "Run Time Frequency":

  • The selected days of the week are completely missing
  • The time is output in 24H format instead of 12H format, in contrast to the dialog where the patch policy is configured.

To Reproduce
Steps to reproduce the behaviour:

  1. Create a Patch Policy with "daily/weekly" frequency (e.g. 11 PM, every Saturday)
  2. Apply the Policy to an Agent
  3. Click Edit on Agent
  4. Switch to the tab "Automation Policies"
  5. "Run Time Frequency" says: "week days: at hour: 23"

Expected behavior

  • output the selected week days
  • output the selected hour in 12H format (or on each other dialogs in 24H format)

Screenshots

Bildschirmfoto vom 2024-08-15 11-17-27

Bildschirmfoto vom 2024-08-15 11-18-05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant