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

Custom attribute for uploading service history for devices #2004

Closed
GMAzrael opened this issue Apr 2, 2018 · 1 comment
Closed

Custom attribute for uploading service history for devices #2004

GMAzrael opened this issue Apr 2, 2018 · 1 comment
Labels
status: duplicate This issue has already been raised

Comments

@GMAzrael
Copy link

GMAzrael commented 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.

@jeremystretch
Copy link
Member

Sounds like this would be covered by #151

@jeremystretch jeremystretch added the status: duplicate This issue has already been raised label Jul 18, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised
Projects
None yet
Development

No branches or pull requests

2 participants