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.

Sign up for GitHub

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

Jump to bottom

Job.interval is interpreted as "seconds" by the UI, but "minutes" in docs #15336

Closed
rixx opened this issue Mar 4, 2024 · 1 comment
Closed

Job.interval is interpreted as "seconds" by the UI, but "minutes" in docs #15336

rixx opened this issue Mar 4, 2024 · 1 comment
Assignees
@jeremystretch
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@rixx
Copy link

rixx commented Mar 4, 2024

Change Type

Correction

Area

Plugins

Proposed Changes

When a plugin creates custom Jobs, both convention (by way of scripts and reports) and documentation state that the interval field is read as minutes. The UI in the detail view however shows the field as "every x seconds":

2024-03-04T16:22:10+01:00

The list view shows the time as minutes in the interval column:

2024-03-04T16:25:07+01:00

Tagging as documentation because "bug" felt a bit dramatic.
@rixx rixx added the type: documentation A change or addition to the documentation label Mar 4, 2024
@jeremystretch
Copy link
Member

Tagging as documentation because "bug" felt a bit dramatic.

I appreciate the hesitation, but this qualifies as a bug. (Documentation issues are limited to changes to the written documentation only; this requires a change to the running code.)

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed type: documentation A change or addition to the documentation labels Mar 8, 2024
@jeremystretch jeremystretch self-assigned this Mar 8, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Mar 8, 2024
@jeremystretch jeremystretch mentioned this issue Mar 13, 2024
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rixx @jeremystretch