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 add contacts to multiple contact groups #10098

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

Originally created by @arosemanhellmann on GitHub (Aug 15, 2024).

Originally assigned to: @arthanson on GitHub.

NetBox version

v4.0.5

Feature type

Data model extension

Proposed functionality

Currently it's only possible to add a contact (person) to one contact group. In our organiszation this does not work out well, as we have only few persons where this 1:1 relation would work. Most of our IT Staff works in multiple (contact)groups. As what i know, in the admin part it's possible (access groups) it's possible to add persons to multipl groups.

It would be nice to have this abbility also in the contact groups.

Use case

Build the source organizational structure in the contacts / contact groups, what currently is not possible for us.

Database changes

No response

External dependencies

No response

Originally created by @arosemanhellmann on GitHub (Aug 15, 2024). Originally assigned to: @arthanson on GitHub. ### NetBox version v4.0.5 ### Feature type Data model extension ### Proposed functionality Currently it's only possible to add a contact (person) to one contact group. In our organiszation this does not work out well, as we have only few persons where this 1:1 relation would work. Most of our IT Staff works in multiple (contact)groups. As what i know, in the admin part it's possible (access groups) it's possible to add persons to multipl groups. It would be nice to have this abbility also in the contact groups. ### Use case Build the source organizational structure in the contacts / contact groups, what currently is not possible for us. ### Database changes _No response_ ### External dependencies _No response_
adam closed this issue 2025-12-29 21:26:50 +01:00
adam commented 2025-12-29 21:26:51 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 15, 2024):

literally asked for the same thing 5 days ago.
https://github.com/netbox-community/netbox/issues/17123

glad this will hopefully get some traction.
@jeremystretch, this being categorized as a breaking change .. does that mean 4.0 to 4.1? or perhaps a point release like 4.1 to 4.1.1 ?

I guess I'm asking if it doesn't go into 4.1 .. would we have to wait until 4.2?

@ghost commented on GitHub (Aug 15, 2024): literally asked for the same thing 5 days ago. https://github.com/netbox-community/netbox/issues/17123 glad this will hopefully get some traction. @jeremystretch, this being categorized as a breaking change .. does that mean 4.0 to 4.1? or perhaps a point release like 4.1 to 4.1.1 ? I guess I'm asking if it doesn't go into 4.1 .. would we have to wait until 4.2?
adam commented 2025-12-29 21:26:51 +01:00
Author
Owner
Copy Link

@arosemanhellmann commented on GitHub (Aug 16, 2024):

https://github.com/netbox-community/netbox/issues/17123 does also focus on sites and site groups / not sure if this is tecnically the same. I'm only focusing on Contacts and Contact Groups. Just wanted to let you know. As what i read above you're planning a change here.

@arosemanhellmann commented on GitHub (Aug 16, 2024): https://github.com/netbox-community/netbox/issues/17123 does also focus on sites and site groups / not sure if this is tecnically the same. I'm only focusing on Contacts and Contact Groups. Just wanted to let you know. As what i read above you're planning a change here.
adam commented 2025-12-29 21:26:51 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 16, 2024):

#17123 does also focus on sites and site groups / not sure if this is tecnically the same. I'm only focusing on Contacts and Contact Groups. Just wanted to let you know. As what i read above you're planning a change here.

I included site groups because the overall concept is the same. The concept is allowing an object to be part of multiple groups of that objects group type.

sites in multiple site groups
contacts in multiple contact groups

the point was consistency. Especially since the documentation outlines site groups as 'role or function' without recognizing that a site or a contact can serve multiple roles or functions. I outlined some examples in https://github.com/netbox-community/netbox/issues/17123.

While sites in multiple site groups would be handy too, if I had to choose, I'd choose contacts being in multiple contact groups.
I also think implementing this would flow nicely into my other FR https://github.com/netbox-community/netbox/issues/17050 which would see the ability to assign contact groups to objects instead of just contacts.

This way, if you are able to place a contact into multiple groups, and then assign contact groups to objects you can much more easily reflect how most companies actually work. (switches having a team assigned as a technical contact, etc.)

@ghost commented on GitHub (Aug 16, 2024): > #17123 does also focus on sites and site groups / not sure if this is tecnically the same. I'm only focusing on Contacts and Contact Groups. Just wanted to let you know. As what i read above you're planning a change here. I included site groups because the overall concept is the same. The concept is allowing an object to be part of multiple groups of that objects group type. sites in multiple site groups contacts in multiple contact groups the point was consistency. Especially since the documentation outlines site groups as 'role or function' without recognizing that a site or a contact can serve multiple roles or functions. I outlined some examples in https://github.com/netbox-community/netbox/issues/17123. While sites in multiple site groups would be handy too, if I had to choose, I'd choose contacts being in multiple contact groups. I also think implementing this would flow nicely into my other FR https://github.com/netbox-community/netbox/issues/17050 which would see the ability to assign contact groups to objects instead of just contacts. This way, if you are able to place a contact into multiple groups, and then assign contact groups to objects you can much more easily reflect how most companies actually work. (switches having a team assigned as a technical contact, etc.)
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 breaking change complexity: medium netbox status: accepted 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#10098
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?