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

Bulk editing Interfaces doesn't support alphanumeric ranges like when you create them #5918

New Issue
Closed
opened 2025-12-29 19:34:14 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:34:14 +01:00
Owner
Copy Link

Originally created by @lucasteinke on GitHub (Jan 10, 2022).

NetBox version

v3.1.5

Python version

3.9

Steps to Reproduce

  1. Select multiple interfaces of a device
  2. Edit them
  3. Enter test[1-42] into the "Label" field
  4. Save

Expected Behavior

Like with bulk creation, where there's a hint "Alphanumeric ranges are supported. (Must match the number of names being created.)", I'd expect the labels to be test1, test2, test3, ..., test42.

Observed Behavior

The labels are all the same, namely test[1-42], so alphanumeric ranges aren't supported in bulk editing.

Originally created by @lucasteinke on GitHub (Jan 10, 2022). ### NetBox version v3.1.5 ### Python version 3.9 ### Steps to Reproduce 1. Select multiple interfaces of a device 2. Edit them 3. Enter `test[1-42]` into the "Label" field 4. Save ### Expected Behavior Like with bulk creation, where there's a hint "Alphanumeric ranges are supported. (Must match the number of names being created.)", I'd expect the labels to be `test1`, `test2`, `test3`, ..., `test42`. ### Observed Behavior The labels are all the same, namely `test[1-42]`, so alphanumeric ranges aren't supported in bulk editing.
adam closed this issue 2025-12-29 19:34:14 +01:00
adam commented 2025-12-29 19:34:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 10, 2022):

This is working as intended. If you'd like to open a feature request, please do so here. Be sure to include a detailed implementation proposal and use case.

@jeremystretch commented on GitHub (Jan 10, 2022): This is working as intended. If you'd like to open a feature request, please do so [here](https://github.com/netbox-community/netbox/issues/new?template=feature_request.md). Be sure to include a detailed implementation proposal and use case.
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
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#5918
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?