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

Ability to bulk rename all relevant models #11054

New Issue
Closed
opened 2025-12-29 21:39:41 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:39:41 +01:00
Owner
Copy Link

Originally created by @mathieumd on GitHub (Apr 17, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.2.7

Feature type

New functionality

Proposed functionality

The table at /ipam/services/ lists all created services attached to a Device or VM.

If you want to rename several of them, you have to edit each of them, one at a time.

It's already possible for interfaces (/dcim/interfaces/, button Rename Selected), so I propose the same feature for services too.

Use case

  1. You named a bunch of services "DNS", but now you need to distinguish between "DNS Resolver" and "DNS Authoritative".
  2. You use Ansible netbox.netbox.nb_inventory with group_by: [ "services" ], and therefore needs a coherent naming (I feel this use case could be improved by #17196)

Database changes

No response

External dependencies

No response

Originally created by @mathieumd on GitHub (Apr 17, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.2.7 ### Feature type New functionality ### Proposed functionality The table at `/ipam/services/` lists all created services attached to a Device or VM. If you want to rename several of them, you have to edit each of them, one at a time. It's already possible for interfaces (`/dcim/interfaces/`, button *Rename Selected*), so I propose the same feature for services too. ### Use case 1. You named a bunch of services "DNS", but now you need to distinguish between "DNS Resolver" and "DNS Authoritative". 2. You use [Ansible netbox.netbox.nb_inventory](https://docs.ansible.com/ansible/latest/collections/netbox/netbox/nb_inventory_inventory.html) with `group_by: [ "services" ]`, and therefore needs a coherent naming (I feel this use case could be improved by #17196) ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:39:41 +01:00
adam closed this issue 2025-12-29 21:39:41 +01:00
adam commented 2025-12-29 21:39:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 20, 2025):

Blocked by #19735

@jeremystretch commented on GitHub (Jun 20, 2025): Blocked by #19735
adam commented 2025-12-29 21:39:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 30, 2025):

This is now open for work, to be implemented in NetBox v4.4 (please target the PR to the feature branch).

@jeremystretch commented on GitHub (Jun 30, 2025): This is now open for work, to be implemented in NetBox v4.4 (please target the PR to the `feature` branch).
adam commented 2025-12-29 21:39:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 30, 2025):

I've expanded the scope of this FR to include all models for which it makes sense to support bulk renaming (i.e. all models with a name field, or similar).

@jeremystretch commented on GitHub (Jun 30, 2025): I've expanded the scope of this FR to include _all_ models for which it makes sense to support bulk renaming (i.e. all models with a `name` field, or similar).
adam commented 2025-12-29 21:39:43 +01:00
Author
Owner
Copy Link

@mathieumd commented on GitHub (Jul 1, 2025):

Excellent, thank you!

@mathieumd commented on GitHub (Jul 1, 2025): Excellent, thank you!
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: low status: accepted 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#11054
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?