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 "site" column to power feed list #8602

New Issue
Closed
opened 2025-12-29 20:38:44 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:38:44 +01:00
Owner
Copy Link

Originally created by @pv2b on GitHub (Sep 12, 2023).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.6.1

Feature type

Change to existing functionality

Proposed functionality

I propose adding "Site" as a selectable column for the power feed view. The power feed model doesn't directly have a "Site" field, so the "Site" column would be populated from the associated Rack.

Use case

When looking at a list of power feeds, it's helpful to, at a glance, know what site the power feed belongs to. This is especially useful if you have duplicate rack names across sites.

Database changes

None.

External dependencies

None.

Originally created by @pv2b on GitHub (Sep 12, 2023). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.6.1 ### Feature type Change to existing functionality ### Proposed functionality I propose adding "Site" as a selectable column for the power feed view. The power feed model doesn't directly have a "Site" field, so the "Site" column would be populated from the associated Rack. ### Use case When looking at a list of power feeds, it's helpful to, at a glance, know what site the power feed belongs to. This is especially useful if you have duplicate rack names across sites. ### Database changes None. ### External dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 20:38:44 +01:00
adam closed this issue 2025-12-29 20:38:44 +01:00
adam commented 2025-12-29 20:38:44 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Sep 12, 2023):

I just realized I can acheive this with a Custom Link, so that's a workaround for now.

If anyone else needs this, just import the following Custom Link using this YAML in the bulk importer:

---
name: Site
content_types: dcim.powerfeed
weight: 1000
button_class: ghost-dark
link_text: '{{ object.rack.site.name }}'
link_url: '{{ object.rack.site.url }}'
enabled: true

Once the Custom Link is created, it can then be used as a field in the table view (which is essentialy what the FR here is asking for.)

The downside to this is that you'll get an extra link on the power feed view to the site, but... I guess that might be considered useful?

Anyway, I still think it should be in Netbox from the start but given it's easy enough to customize Netbox and get the same result this probably doesn't need to be prioritized.

@pv2b commented on GitHub (Sep 12, 2023): I just realized I can acheive this with a Custom Link, so that's a workaround for now. If anyone else needs this, just import the following Custom Link using this YAML in the bulk importer: ```yaml --- name: Site content_types: dcim.powerfeed weight: 1000 button_class: ghost-dark link_text: '{{ object.rack.site.name }}' link_url: '{{ object.rack.site.url }}' enabled: true ``` Once the Custom Link is created, it can then be used as a field in the table view (which is essentialy what the FR here is asking for.) The downside to this is that you'll get an extra link on the power feed view to the site, but... I guess that might be considered useful? Anyway, I still think it should be in Netbox from the start but given it's easy enough to customize Netbox and get the same result this probably doesn't need to be prioritized.
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#8602
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?