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 Roles Groups #6706

New Issue
Closed
opened 2025-12-29 19:44:19 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:44:19 +01:00
Owner
Copy Link

Originally created by @dg2assassin on GitHub (Jul 21, 2022).

NetBox version

v3.2.7

Feature type

Data model extension

Proposed functionality

Propose grouping of rack roles similar to how locations function. This will better organize the rack roles page and allow grouping racks based on a system's purpose and the function each rack provides within said system.

Use case

I work with OT networks where we deal with systems on a functional level. Each system provides a specific role, and each rack usually has a single function that is not replicated in other racks. This has lead us to have a large amount of rack roles with no real way to organize them outside of using tags. While tags work, it would be great to have the ability to group system specific roles into a single group. The idea being similar to how the location page works.

Few examples:

  • Digital Control System

    • Primary Data Servers
    • Pump Controls
    • Pressurizer Controls

  • Security System

    • Video Management
      • Video Recorders
      • Encoder Blades

Database changes

I'm not overly well versed with the netbox database, but I would assuming the following fields would need to be added to the rack role table:

  • parent_id
  • parent
  • child_id?

External dependencies

No external dependencies are needed for this feature request.

Originally created by @dg2assassin on GitHub (Jul 21, 2022). ### NetBox version v3.2.7 ### Feature type Data model extension ### Proposed functionality Propose grouping of rack roles similar to how locations function. This will better organize the rack roles page and allow grouping racks based on a system's purpose and the function each rack provides within said system. ### Use case I work with OT networks where we deal with systems on a functional level. Each system provides a specific role, and each rack usually has a single function that is not replicated in other racks. This has lead us to have a large amount of rack roles with no real way to organize them outside of using tags. While tags work, it would be great to have the ability to group system specific roles into a single group. The idea being similar to how the location page works. Few examples: - Digital Control System - Primary Data Servers - Pump Controls - Pressurizer Controls - Security System - Video Management - Video Recorders - Encoder Blades ### Database changes I'm not overly well versed with the netbox database, but I would assuming the following fields would need to be added to the rack role table: - parent_id - parent - child_id? ### External dependencies No external dependencies are needed for this feature request.
adam added the type: feature label 2025-12-29 19:44:19 +01:00
adam closed this issue 2025-12-29 19:44:20 +01:00
adam commented 2025-12-29 19:44:20 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jul 24, 2022):

IF this were to be evaluated, I would imagine anything with a role would be on the table for either nesting roles or creating a parent group instead of just tackling for racks.

IE likely a duplicate of #9643

@ryanmerolle commented on GitHub (Jul 24, 2022): IF this were to be evaluated, I would imagine anything with a role would be on the table for either nesting roles or creating a parent group instead of just tackling for racks. IE likely a duplicate of #9643
adam commented 2025-12-29 19:44:21 +01:00
Author
Owner
Copy Link

@dg2assassin commented on GitHub (Jul 25, 2022):

ah ok. I was focused on rack role groups, and didn't expand my search for all role groups which is how I missed 9643.

@dg2assassin commented on GitHub (Jul 25, 2022): ah ok. I was focused on rack role groups, and didn't expand my search for all role groups which is how I missed 9643.
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 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#6706
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?