starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Support alphanumeric ranges when bulk editing components #10495

New Issue
Closed
opened 2025-12-29 21:32:15 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:32:15 +01:00
Owner
Copy Link

Originally created by @99-lives on GitHub (Nov 21, 2024).

NetBox version

v4.1.6

Feature type

New functionality

Triage priority

N/A

Proposed functionality

Hello,

I've started using Netbox in my workplace recently, and the main workflow challenge I've encountered, is when I want to bulk edit the labels of components on a device. I propose that Netbox add support for inputting alphanumeric ranges in the label field of the bulk component edit form. This would function similarly to creating a range of components, where the label range must match the number of components being created, or in this case, edited.

Use case

My use case is for labeling patch panels. If I have a several 24 port patch panels, I can create a device type for it, which has 24x front and rear ports, all with the correct port type. Every patch panel device will have ports with the same name (1 to 24).
But when actually creating multiple devices from this type, I want to update the front port labels to be 1 to 24, then 25 to 49, 49 to 72, etc.

I can work around this by deleting and recreating the front ports, but this requires matching the other fields to my preferred values, such as the type, color, description, etc. If I have already specified my preferred values on the device type, then I should not need to input them a second time. It would be ideal if I could bulk rename all the label fields using a range expression.
Deleting and recreating would also not work if one wanted to relabel a bunch of interfaces that had cable connections, as the cables would be deleted.

Thank you for your consideration.

Database changes

None.

External dependencies

None. The infrastructure for inputting and validating alphanumeric ranges already exists.

Originally created by @99-lives on GitHub (Nov 21, 2024). ### NetBox version v4.1.6 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality Hello, I've started using Netbox in my workplace recently, and the main workflow challenge I've encountered, is when I want to bulk edit the labels of components on a device. I propose that Netbox add support for inputting alphanumeric ranges in the label field of the bulk component edit form. This would function similarly to creating a range of components, where the label range must match the number of components being created, or in this case, edited. ### Use case My use case is for labeling patch panels. If I have a several 24 port patch panels, I can create a device type for it, which has 24x front and rear ports, all with the correct port type. Every patch panel device will have ports with the same name (1 to 24). But when actually creating multiple devices from this type, I want to update the front port labels to be 1 to 24, then 25 to 49, 49 to 72, etc. I can work around this by deleting and recreating the front ports, but this requires matching the other fields to my preferred values, such as the type, color, description, etc. If I have already specified my preferred values on the device type, then I should not need to input them a second time. It would be ideal if I could bulk rename all the label fields using a range expression. Deleting and recreating would also not work if one wanted to relabel a bunch of interfaces that had cable connections, as the cables would be deleted. Thank you for your consideration. ### Database changes None. ### External dependencies None. The infrastructure for inputting and validating alphanumeric ranges already exists.
adam added the type: featurestatus: needs ownerpending closurecomplexity: medium labels 2025-12-29 21:32:15 +01:00
adam closed this issue 2025-12-29 21:32:15 +01:00
adam commented 2025-12-29 21:32:15 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 13, 2025):

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 (May 13, 2025): 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/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:32:15 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 12, 2025):

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 (Jun 12, 2025): 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.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label complexity: medium pending closure status: needs owner type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10495
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?