starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2025-12-29 20:48:18 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:48:18 +01:00
Owner
Copy Link

Originally created by @rixx on GitHub (Mar 4, 2024).

Originally assigned to: @jeremystretch on GitHub.

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.

Originally created by @rixx on GitHub (Mar 4, 2024). Originally assigned to: @jeremystretch on GitHub. ### 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](https://github.com/netbox-community/netbox/assets/2657547/fecb0c00-1131-497e-addd-3f338a5ad375) The list view shows the time as minutes in the interval column: ![2024-03-04T16:25:07+01:00](https://github.com/netbox-community/netbox/assets/2657547/09b0b361-1434-419f-8ed6-344ed327ee24) Tagging as documentation because "bug" felt a bit dramatic.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:48:18 +01:00
adam closed this issue 2025-12-29 20:48:18 +01:00
adam commented 2025-12-29 20:48:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 8, 2024):

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 commented on GitHub (Mar 8, 2024): > 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.)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label severity: low status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9313
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?