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

Status field for modules #10371

Closed
severgun opened this issue Sep 15, 2022 · 3 comments
Closed

Status field for modules #10371

severgun opened this issue Sep 15, 2022 · 3 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@severgun
Copy link

NetBox version

v3.3.2

Feature type

Data model extension

Proposed functionality

Would be nice to have state field for modules.
Active, Failed, somethink like that.

Use case

For example there is device with failed Fan. Replacement part is scheduled for delivery, but currently failed module stays in slot and would be nice to have ability to keep track of that fact.

Database changes

Add new field 'status' to modules.

External dependencies

No response

@severgun severgun added the type: feature Introduction of new functionality to the application label Sep 15, 2022
@severgun
Copy link
Author

Nevermind. Custom fields are here for that.

@severgun severgun closed this as not planned Won't fix, can't repro, duplicate, stale Sep 15, 2022
@jeremystretch
Copy link
Member

Nevermind. Custom fields are here for that.

Custom fields can work certainly, however I think it's worth exploring interest in a native status field for modules. I think it could be generally useful.

@jeremystretch jeremystretch reopened this Sep 15, 2022
@jeremystretch jeremystretch added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Sep 15, 2022
@jeremystretch jeremystretch changed the title State value for modules Status field for modules Sep 15, 2022
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Nov 15, 2022
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Nov 15, 2022
@jeremystretch jeremystretch added this to the v3.4 milestone Dec 9, 2022
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed needs milestone Awaiting prioritization for inclusion with a future NetBox release labels Dec 9, 2022
@jeremystretch jeremystretch self-assigned this Dec 9, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants