starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 13:00:30 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow for multiple groups / classes for locations & sites #11950

New Issue
Open
opened 2025-12-29 21:51:50 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:51:50 +01:00
Owner
Copy Link

Originally created by @PetitPrinc3 on GitHub (Dec 27, 2025).

NetBox version

v4.4.9

Feature type

Data model extension

Proposed functionality

Hi,

Thank you for your incredible work on netbox.

I would like to be able to add a "Room Types" field to the "location" and/or "sites" model.
This would allow one to filter the data based on fileds like : floor, room type (technical, office, ...), whatever you feel like.

Location :

I've tried to use a "Custom Field" using "Site Groups" as classes and having them in a list :

Image

However, despite this, the location object isn't "linked" to the selected site groups therefore making filtering impossible :

Image

Sites :

For sites, it is only possible to add one "Group Site". Having a list of "Group Sites" rather than a single entry could make the functionality described above operational.

Image

Thanks for your help and time !

Best

Use case

As explained above, this could be usefull to sort locations/rooms based on their "memberships".
Examples :

  • I want to only see the rooms on "floor 1"
  • I want to see the "server" rooms "on floor 3"

This is mostly relevant for topology views.

Database changes

Location :

  • New table : dcim_location_group
  • New column in dcim_location : group_ids (list of groups)

Sites :

  • Alter column in dcim_site : group_id becomes group_ids (list of groups)

External dependencies

None

Originally created by @PetitPrinc3 on GitHub (Dec 27, 2025). ### NetBox version v4.4.9 ### Feature type Data model extension ### Proposed functionality Hi, Thank you for your incredible work on netbox. I would like to be able to add a "Room Types" field to the "location" and/or "sites" model. This would allow one to filter the data based on fileds like : floor, room type (technical, office, ...), whatever you feel like. ### Location : I've tried to use a "Custom Field" using "Site Groups" as classes and having them in a list : <img width="1158" height="1223" alt="Image" src="https://github.com/user-attachments/assets/1e63df61-3ddf-4acd-ad8b-e766e7828c20" /> However, despite this, the location object isn't "linked" to the selected site groups therefore making filtering impossible : <img width="2315" height="1114" alt="Image" src="https://github.com/user-attachments/assets/ae955ba0-daea-474a-a4bc-7c8a74cd6169" /> ### Sites : For sites, it is only possible to add one "Group Site". Having a list of "Group Sites" rather than a single entry could make the functionality described above operational. <img width="1256" height="1214" alt="Image" src="https://github.com/user-attachments/assets/a6ee2b87-7bcd-4066-b480-f3eb952ce1a7" /> Thanks for your help and time ! Best ### Use case As explained above, this could be usefull to sort locations/rooms based on their "memberships". Examples : - I want to only see the rooms on "floor 1" - I want to see the "server" rooms "on floor 3" This is mostly relevant for topology views. ### Database changes ### Location : - New table : dcim_location_group - New column in dcim_location : group_ids (list of groups) ### Sites : - Alter column in dcim_site : group_id becomes group_ids (list of groups) ### External dependencies None
adam added the type: featurenetboxstatus: needs triage labels 2025-12-29 21:51:50 +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 netbox status: needs triage 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#11950
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?