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

rack_group missing from power feed add/view #2982

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

Originally created by @bellwood on GitHub (Oct 28, 2019).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.6.6

Steps to Reproduce

  1. Import a new power feed, fill all fields (including the rack_group)
  2. View the feed

Expected Behavior

Feed add/view should include rack_group

Observed Behavior

Feed add/view is missing rack_group

Additional Details

Pursuant to: 800df1ebbe

Edit: Sorry for so many edits... Powerfeeds as a whole need to be reviewed to add in rack_group. It's also missing from the sidebar search, there's no heading for it when listing all power feeds, etc.

Originally created by @bellwood on GitHub (Oct 28, 2019). ### Environment * Python version: 3.6.9 * NetBox version: 2.6.6 ### Steps to Reproduce 1. Import a new power feed, fill all fields (including the rack_group) 2. View the feed <!-- What did you expect to happen? --> ### Expected Behavior Feed add/view should include rack_group <!-- What happened instead? --> ### Observed Behavior Feed add/view is missing rack_group ### Additional Details Pursuant to: 800df1ebbe151b21dae14f96d950afbe35b10e68 Edit: Sorry for so many edits... Powerfeeds as a whole need to be reviewed to add in rack_group. It's also missing from the sidebar search, there's no heading for it when listing all power feeds, etc.
adam added the status: under review label 2025-12-29 18:24:20 +01:00
adam closed this issue 2025-12-29 18:24:20 +01:00
adam commented 2025-12-29 18:24:21 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Nov 2, 2019):

Power panel view shows Both Rack Group and Power Feeds. Is it not good?

Screenshot from 2019-11-02 03-27-16

@kobayashi commented on GitHub (Nov 2, 2019): Power panel view shows Both Rack Group and Power Feeds. Is it not good? ![Screenshot from 2019-11-02 03-27-16](https://user-images.githubusercontent.com/8712070/68067649-d2448f00-fd20-11e9-917f-a4e638cd5210.png)
adam commented 2025-12-29 18:24:21 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Nov 4, 2019):

We've a lot of common naming in our IX unique to individual rack groups. Having to jump to a power panel just to see what rack_group its' in versus having it right with the rest of the data in view is sub-optimal from a work flow standpoint.

I suppose leaving it out of the tabular list of power feeds is OK if we can add filtering by rack_group in that view.

Edit: It would still be preferred to show the rack group on individual power feeds views as well.

@bellwood commented on GitHub (Nov 4, 2019): We've a lot of common naming in our IX unique to individual rack groups. Having to jump to a power panel just to see what rack_group its' in versus having it right with the rest of the data in view is sub-optimal from a work flow standpoint. I suppose leaving it out of the tabular list of power feeds is OK if we can add filtering by rack_group in that view. Edit: It would still be preferred to show the rack group on individual power feeds views as well.
adam commented 2025-12-29 18:24:21 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Nov 5, 2019):

I would like to know more about your point. At power panel list view, you can search desired rack group and see the relation between rack group and power feed inside the searched power panel. Does this not fit your workflow?

If we would add rack_group to the page, we have to retrieve nested objects. This may effect for other pages now. This is because the list and search are included from shared template files which show related objects excluding nested for the display object.

@kobayashi commented on GitHub (Nov 5, 2019): I would like to know more about your point. At power panel list view, you can search desired rack group and see the relation between rack group and power feed inside the searched power panel. Does this not fit your workflow? If we would add rack_group to the page, we have to retrieve nested objects. This may effect for other pages now. This is because the list and search are included from shared template files which show related objects excluding nested for the display object.
adam commented 2025-12-29 18:24:22 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Dec 5, 2019):

@bellwood do you still have any comments for this? If you still have any questions or concerns about this issue, plz let me know to re-open.

@kobayashi commented on GitHub (Dec 5, 2019): @bellwood do you still have any comments for this? If you still have any questions or concerns about this issue, plz let me know to re-open.
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: under review
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#2982
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?