Add Enable/Disable interface quick action in device view #7113

Closed
opened 2025-12-29 20:19:22 +01:00 by adam · 4 comments
Owner

Originally created by @etfz on GitHub (Oct 17, 2022).

NetBox version

v3.2.5

Feature type

New functionality

Proposed functionality

Add a quick action button for toggling active state of an interface near or inside the Edit/Delete menu, and possibly also one below the table for bulk toggling.

Use case

Enabling or disabling interfaces seems to me like a basic and common task that could be more readily available. The per interface quick action bar is starting to get a bit cluttered, but if placed in the Edit menu I feel like that should not be an issue.

Database changes

No response

External dependencies

No response

Originally created by @etfz on GitHub (Oct 17, 2022). ### NetBox version v3.2.5 ### Feature type New functionality ### Proposed functionality Add a quick action button for toggling active state of an interface near or inside the Edit/Delete menu, and possibly also one below the table for bulk toggling. ### Use case Enabling or disabling interfaces seems to me like a basic and common task that could be more readily available. The per interface quick action bar is starting to get a bit cluttered, but if placed in the Edit menu I feel like that should not be an issue. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:19:22 +01:00
adam closed this issue 2025-12-29 20:19:23 +01:00
Author
Owner

@chambersh1129 commented on GitHub (Nov 9, 2022):

I'd like to work on this. Design wise, I see the yellow Edit/Rename and red Delete/Disconnect button at the bottom of an interface table when looking at a device. Would a green "Enable" and red "Disable" button suffice?

For the backend I would look to create a new view/url, something similar to the dcim/views/BulkDisconnectView because a generic likely doesn't exist. Should it prompt the user with an "are you sure" like the bulk disconnect/delete does or jshould it ust enable/disable based on the button pressed then return?

Alternatively, this is already supported in a way. You can select multiple interfaces, click the "Edit" button at the bottom of the table, and enable/disable the port from there. It is a few extra clicks, but it is still bulk editing multiple ports so this feature may not be needed.

@chambersh1129 commented on GitHub (Nov 9, 2022): I'd like to work on this. Design wise, I see the yellow Edit/Rename and red Delete/Disconnect button at the bottom of an interface table when looking at a device. Would a green "Enable" and red "Disable" button suffice? For the backend I would look to create a new view/url, something similar to the dcim/views/BulkDisconnectView because a generic likely doesn't exist. Should it prompt the user with an "are you sure" like the bulk disconnect/delete does or jshould it ust enable/disable based on the button pressed then return? Alternatively, this is already supported in a way. You can select multiple interfaces, click the "Edit" button at the bottom of the table, and enable/disable the port from there. It is a few extra clicks, but it is still bulk editing multiple ports so this feature may not be needed.
Author
Owner

@etfz commented on GitHub (Nov 25, 2022):

As far as I'm concerned that all sounds good. A confirmation dialog for bulk toggling seems sensible. I am aware of the existing functionality.

I am at least as interested in the functionality of individual interface toggles.

@etfz commented on GitHub (Nov 25, 2022): As far as I'm concerned that all sounds good. A confirmation dialog for bulk toggling seems sensible. I am aware of the existing functionality. I am at least as interested in the functionality of individual interface toggles.
Author
Owner

@github-actions[bot] commented on GitHub (Jan 25, 2023):

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[bot] commented on GitHub (Jan 25, 2023): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Feb 25, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Feb 25, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7113