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

Bulk operation background jobs should utilize new job logging mechanism #11444

New Issue
Closed
opened 2025-12-29 21:45:18 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:45:18 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Aug 1, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

feature @ ae425d9da9

Feature type

Change to existing functionality

Proposed functionality

When executing a bulk operation (e.g. editing multiple sites) as a background job, any logged data should be stored using the job logging mechanism introduced in #19816.

Use case

Utilizing the logging mechanism results in properly formatted and timestamped log messages, vastly improving user experience as compared to storing messages as raw job data.

Database changes

N/A

External dependencies

N/A

Originally created by @jeremystretch on GitHub (Aug 1, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version feature @ ae425d9da956ee301ea8f0dd2e45bdc67c8608cd ### Feature type Change to existing functionality ### Proposed functionality When executing a bulk operation (e.g. editing multiple sites) as a background job, any logged data should be stored using the job logging mechanism introduced in #19816. ### Use case Utilizing the logging mechanism results in properly formatted and timestamped log messages, vastly improving user experience as compared to storing messages as raw job data. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:45:18 +01:00
adam closed this issue 2025-12-29 21:45:19 +01:00
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 complexity: low status: accepted type: feature
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#11444
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?