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 location field to "Add Power Feed" form #7220

New Issue
Closed
opened 2025-12-29 20:20:36 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:20:36 +01:00
Owner
Copy Link

Originally created by @fabi125 on GitHub (Nov 11, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.3.5

Feature type

Change to existing functionality

Proposed functionality

When creating a new Power Feed via the UI, the form only lets you select a rack, it would be great if the form would also expose a Location selector and then filter the available Racks based on that selection (similar to how the Site choices are limited by a selected Region).

Use case

We have racks with the same name in the same site but within a different location. That makes it non-obvious which is the right rack to select.

Database changes

Being able to specify a Location is already possible when using the Bulk Import feature, so we don't think this should require any database changes.

External dependencies

n/a

Originally created by @fabi125 on GitHub (Nov 11, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.3.5 ### Feature type Change to existing functionality ### Proposed functionality When creating a new Power Feed via the UI, the form only lets you select a rack, it would be great if the form would also expose a Location selector and then filter the available Racks based on that selection (similar to how the Site choices are limited by a selected Region). ### Use case We have racks with the same name in the same site but within a different location. That makes it non-obvious which is the right rack to select. ### Database changes Being able to specify a Location is already possible when using the Bulk Import feature, so we don't think this should require any database changes. ### External dependencies n/a
adam added the status: acceptedtype: feature labels 2025-12-29 20:20:36 +01:00
adam closed this issue 2025-12-29 20:20:36 +01:00
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 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#7220
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?