Skip to content

Add ability to have 'sites' and 'contacts' be members of multiple groups #17123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
goteamkor opened this issue Aug 10, 2024 · 1 comment
Closed
Labels
status: duplicate This issue has already been raised type: feature Introduction of new functionality to the application

Comments

@goteamkor
Copy link

goteamkor commented 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.

@goteamkor goteamkor added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Aug 10, 2024
@arthanson arthanson removed their assignment Aug 12, 2024
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation complexity: medium Requires a substantial but not unusual amount of effort to implement and removed status: needs triage This issue is awaiting triage by a maintainer labels Aug 12, 2024
@jeremystretch
Copy link
Member

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

@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Aug 12, 2024
@jeremystretch jeremystretch added status: duplicate This issue has already been raised and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation complexity: medium Requires a substantial but not unusual amount of effort to implement labels Aug 12, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants