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 ability to have 'sites' and 'contacts' be members of multiple groups #10070

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

Originally created by @ghost on GitHub (Aug 10, 2024).

NetBox version

v.4.0.8

Feature type

Change to existing functionality

Proposed functionality

Add the ability for 'Sites' and 'Contacts' to be members of multiple 'site groups', and 'contact groups'.

Use case

Site groups are defined in the documentation as:

Whereas regions are intended to provide geographic organization, site groups can be used to classify sites by role or function.

In many businesses a site can have multiple roles or functions.
For example, let's say my company is broken out into multiple product lines. I might have a single tenant (corporate), but multiple site groups for each product line. Some sites might produce multiple product lines rather than just 1.

Contact groups are similar. Let's suppose we have the following contact group hierarchy.

  • Internal
    • Infrastructure
      • Network
      • Systems
      • Database
    • Applications
      • ERP

In this case, I might have a network engineer part of the 'network' contact group, and a systems engineer part of the 'systems' contact group. But I might also have an employee that has equal skills for both network and systems. There currently is no way to model this person being able to be part of both the network and systems contact groups.
Putting this user one level higher (infrastructure) wouldn't make sense in the scenario above because Infrastructure also contains 'database', (and perhaps other teams too). Thus it might appear this network/systems person has skills for database and other teams too, when that isn't the case.
Or another example might be a reporting structure. Let's say we have a manager that supervises both the network and systems teams (but not the database team). It would be handy to place that manager in both the network and systems contact groups to reflect their responsibility for those groups.

The drop down selector for site groups and contact groups would need to change from a single object selection to a multi-object selection (like tags are now)

Database changes

Change the field that stores site groups and contact groups from single object to multi-object.
Database field would need to change from single value to array.

External dependencies

None.

Originally created by @ghost on GitHub (Aug 10, 2024). ### NetBox version v.4.0.8 ### Feature type Change to existing functionality ### Proposed functionality Add the ability for 'Sites' and 'Contacts' to be members of multiple 'site groups', and 'contact groups'. ### Use case Site groups are defined in the documentation as: > Whereas regions are intended to provide geographic organization, site groups can be used to classify sites by role or function. In many businesses a site can have multiple roles or functions. For example, let's say my company is broken out into multiple product lines. I might have a single tenant (corporate), but multiple site groups for each product line. Some sites might produce multiple product lines rather than just 1. Contact groups are similar. Let's suppose we have the following contact group hierarchy. - Internal - Infrastructure - Network - Systems - Database - Applications - ERP In this case, I might have a network engineer part of the 'network' contact group, and a systems engineer part of the 'systems' contact group. But I might also have an employee that has equal skills for both network **and** systems. There currently is no way to model this person being able to be part of both the network and systems contact groups. Putting this user one level higher (infrastructure) wouldn't make sense in the scenario above because Infrastructure also contains 'database', (and perhaps other teams too). Thus it might appear this network/systems person has skills for database and other teams too, when that isn't the case. Or another example might be a reporting structure. Let's say we have a manager that supervises both the network and systems teams (but not the database team). It would be handy to place that manager in both the network and systems contact groups to reflect their responsibility for those groups. The drop down selector for site groups and contact groups would need to change from a single object selection to a multi-object selection (like tags are now) ### Database changes Change the field that stores site groups and contact groups from single object to multi-object. Database field would need to change from single value to array. ### External dependencies None.
adam added the type: featurestatus: duplicate labels 2025-12-29 21:26:26 +01:00
adam closed this issue 2025-12-29 21:26:27 +01:00
adam commented 2025-12-29 21:26:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 12, 2024):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #10784 for further discussion.

@jeremystretch commented on GitHub (Aug 12, 2024): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #10784 for further discussion.
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: duplicate 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#10070
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?