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

Allow all Interface bulk-edit fields to be set to "don't change" #5444

Closed
steffann opened this issue Dec 11, 2020 · 2 comments
Closed

Allow all Interface bulk-edit fields to be set to "don't change" #5444

steffann opened this issue Dec 11, 2020 · 2 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@steffann
Copy link
Contributor

Environment

  • Python version: 3.7.3
  • NetBox version: v2.9.10

Proposed Functionality

I noticed that when bulk-editing multiple interfaces there is only an "Enabled" checkbox which affects all the selected interfaces. I propose to change that checkbox so that it becomes possible to leave the enabled state of the interfaces unchanged.

The same is true for the "OOB Management" checkbox.

Use Case

If you currently want to change a property of multiple interfaces, some of which are enabled and some of which are disabled, you'd either have to do the change twice (once for the enabled and once for the disabled interfaces) or, which happens to me sometimes, I make a change to the interfaces, realise I accidentally enabled some interfaces, and then disable them again.

The "OOB Management" checkbox works in the same way, so I'd suggest changing them both. It would be very useful if the default setting for all the fields in the bulk-edit is "don't change".

Database Changes

None

External Dependencies

None

Implementation volunteering

I'd be happy to

@DanSheps DanSheps added status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application labels Dec 14, 2020
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application labels Dec 15, 2020
@jeremystretch jeremystretch self-assigned this Dec 15, 2020
@steffann
Copy link
Contributor Author

That only seems to fix it for the mgmt_only field. Am I missing something?

@jeremystretch
Copy link
Member

Missed that, thanks!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 16, 2021
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: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants