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

Add variable option to bulk-edit feature #2179

New Issue
Closed
opened 2025-12-29 17:23:04 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:23:04 +01:00
Owner
Copy Link

Originally created by @swerveshot on GitHub (Dec 7, 2018).

Environment

NetBox version: 2.4.8

Proposed Functionality

It would be really nice to have the ability to add a variable option to the bulk-edit feature. This feature would work sort of like the range option that is available with the naming of ports.

So how would this work in practice?

Let's say I have a large number of VLANs and wanted to edit the names of the selection to have them include the VLAN ID.

  1. First I select the appropriate VLANs and then hit the edit link.
  2. Then on the actual edit page I'd like to have a dropdown menu containing every text field and below that a field where one can enter a value.
  3. The value could be static or contain variables like such: [vlanname]-[vid]

Maybe using the square brackets is confusing because they are also used for ranges. But it's just an example.

Use Case

I recently ran into issue #1823 and wanted to quickly change a large number of VLAN names to make them unique. The proposed feature would accomplish this in the UI rather than having to do this via the API.

You could also reconsider re-opening issue #1823 but I can think of other use cases where this feature might be useful. 😆

API changes

You could make this feature available through the API but my use case is mostly for the UI.

Originally created by @swerveshot on GitHub (Dec 7, 2018). ### Environment NetBox version: 2.4.8 ### Proposed Functionality It would be really nice to have the ability to add a variable option to the bulk-edit feature. This feature would work sort of like the range option that is available with the naming of ports. So how would this work in practice? Let's say I have a large number of VLANs and wanted to edit the names of the selection to have them include the VLAN ID. 1. First I select the appropriate VLANs and then hit the edit link. 2. Then on the actual edit page I'd like to have a dropdown menu containing every text field and below that a field where one can enter a value. 3. The value could be static or contain variables like such: `[vlanname]-[vid]` Maybe using the square brackets is confusing because they are also used for ranges. But it's just an example. ### Use Case I recently ran into issue #1823 and wanted to quickly change a large number of VLAN names to make them unique. The proposed feature would accomplish this in the UI rather than having to do this via the API. You _could_ also reconsider re-opening issue #1823 but I can think of other use cases where this feature might be useful. 😆 ### API changes You could make this feature available through the API but my use case is mostly for the UI.
adam closed this issue 2025-12-29 17:23:04 +01:00
adam commented 2025-12-29 17:23:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 11, 2018):

I don't like the idea of implementing this much complexity in the bulk edit feature. It was only ever intended to be a convenience. Once you get to the point of doing variable substitution inside properties, you really should be working with the API or shell.

@jeremystretch commented on GitHub (Dec 11, 2018): I don't like the idea of implementing this much complexity in the bulk edit feature. It was only ever intended to be a convenience. Once you get to the point of doing variable substitution inside properties, you really should be working with the API or shell.
adam commented 2025-12-29 17:23:05 +01:00
Author
Owner
Copy Link

@swerveshot commented on GitHub (Dec 11, 2018):

Ahw man, a thumbs down. That's too bad. I get your point and guess I should be getting familiar with the Python requests library real soon. Still I appreciate that you labeled the request with a 'gathering feedback' label to give others a chance to comment.

@swerveshot commented on GitHub (Dec 11, 2018): Ahw man, a thumbs down. That's too bad. I get your point and guess I should be getting familiar with the Python requests library real soon. Still I appreciate that you labeled the request with a 'gathering feedback' label to give others a chance to comment.
adam commented 2025-12-29 17:23:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 4, 2019):

Closing this out as there's been no additional feedback, and honestly it's not a path I want to go down.

@jeremystretch commented on GitHub (Jan 4, 2019): Closing this out as there's been no additional feedback, and honestly it's not a path I want to go down.
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#2179
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?