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

Custom attribute for uploading service history for devices #1653

New Issue
Closed
opened 2025-12-29 16:33:59 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:33:59 +01:00
Owner
Copy Link

Originally created by @GMAzrael on GitHub (Apr 2, 2018).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version:
  • NetBox version:

Description

Having the ability to attribute a log of work done to devices with an upload or templatized documentation format (RST/Markdown etc.) would be handy.

Use case 1. Bob uploaded a configuration change to a switch. His change management process dictates he have a document in txt format that shows the before and after configuration changes for the change. The document upload is timestamped. After making the change, Bob wants to see when the system changed prior to that one.

Use Case 2. Jim is having a number of problem with a Server. Thinking back, he know a manufacturer technician has worked on a system a number of time. He logs in to NetBox and looks at the service history. He sees a number of parts have been replaced in the last 3 months. Recommends a replacement for the next time the system fails.

Implimentation:

The ability to add an uploadable field for a device, similar to the media section for rack/device images. History is tracked by device ID and timestamped with the upload date. Files are some flavor of text base for small size.

Originally created by @GMAzrael on GitHub (Apr 2, 2018). ### Issue type [X] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: <!-- Example: 3.5.4 --> * NetBox version: <!-- Example: 2.1.3 --> ### Description Having the ability to attribute a log of work done to devices with an upload or templatized documentation format (RST/Markdown etc.) would be handy. Use case 1. Bob uploaded a configuration change to a switch. His change management process dictates he have a document in txt format that shows the before and after configuration changes for the change. The document upload is timestamped. After making the change, Bob wants to see when the system changed prior to that one. Use Case 2. Jim is having a number of problem with a Server. Thinking back, he know a manufacturer technician has worked on a system a number of time. He logs in to NetBox and looks at the service history. He sees a number of parts have been replaced in the last 3 months. Recommends a replacement for the next time the system fails. Implimentation: The ability to add an uploadable field for a device, similar to the media section for rack/device images. History is tracked by device ID and timestamped with the upload date. Files are some flavor of text base for small size.
adam added the status: duplicate label 2025-12-29 16:33:59 +01:00
adam closed this issue 2025-12-29 16:33:59 +01:00
adam commented 2025-12-29 16:34:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2018):

Sounds like this would be covered by #151

@jeremystretch commented on GitHub (Jul 18, 2018): Sounds like this would be covered by #151
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 status: duplicate
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#1653
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?