Add ability to bulk rename interface labels during interface rename #6888

Closed
opened 2025-12-29 19:46:21 +01:00 by adam · 2 comments
Owner

Originally created by @ghost on GitHub (Aug 27, 2022).

NetBox version

v3.3.0

Feature type

New functionality

Proposed functionality

Currently, when you bulk rename interfaces, the operation will only update the 'name' of the interface.
The RegEx rename operation should also allow the ability to update the interfaces label at the same time.

Use case

Often, our interface 'name' and the interface 'label' are the same.
When bulk renaming interfaces (for fixing interface names in a switch stack scenario) we are left with interface names and interface labels that no longer match.

Perhaps just a check box in the rename process that says 'update interface label' or something to that effect.

Database changes

None.

External dependencies

None.

Originally created by @ghost on GitHub (Aug 27, 2022). ### NetBox version v3.3.0 ### Feature type New functionality ### Proposed functionality Currently, when you bulk rename interfaces, the operation will only update the 'name' of the interface. The RegEx rename operation should also allow the ability to update the interfaces label at the same time. ### Use case Often, our interface 'name' and the interface 'label' are the same. When bulk renaming interfaces (for fixing interface names in a switch stack scenario) we are left with interface names and interface labels that no longer match. Perhaps just a check box in the rename process that says 'update interface label' or something to that effect. ### Database changes None. ### External dependencies None.
adam added the type: featurepending closure labels 2025-12-29 19:46:21 +01:00
adam closed this issue 2025-12-29 19:46:21 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 26, 2022):

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 (Oct 26, 2022): 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 (Nov 26, 2022):

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 (Nov 26, 2022): 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#6888