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

Allow Tenant to be in multiple Tenant-Groups #2315

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

Originally created by @tb-killa on GitHub (Jan 28, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.5.2

Proposed Functionality

Allow Tenant to be in multiple Tenant-Groups.
Actually if you select a Tenant to one Tenant-Group you couldn´t allow the to be in another Group too.

Use Case

If you have multiple Tenant wo you would assign for Documentation into Groups you could only allow the to one Tenant-Group. If you have multiple customers who you would documentate withing different Groups it wouldn´t work actually.
Maybe with the new "select2" we could bring in some Sort of Multi-Select-Boxes like with Tags.

Database Changes

Yes

External Dependencies

No

Originally created by @tb-killa on GitHub (Jan 28, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 * NetBox version: 2.5.2 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Allow Tenant to be in multiple Tenant-Groups. Actually if you select a Tenant to one Tenant-Group you couldn´t allow the to be in another Group too. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case If you have multiple Tenant wo you would assign for Documentation into Groups you could only allow the to one Tenant-Group. If you have multiple customers who you would documentate withing different Groups it wouldn´t work actually. Maybe with the new "select2" we could bring in some Sort of Multi-Select-Boxes like with Tags. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Yes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies No
adam closed this issue 2025-12-29 17:24:44 +01:00
adam commented 2025-12-29 17:24:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 29, 2019):

I have to reject this as it would upset a long-established relational model. Groups are intended to serve as organizational units for tenants, not classifications. I'd recommend using tags for the later.

@jeremystretch commented on GitHub (Jan 29, 2019): I have to reject this as it would upset a long-established relational model. Groups are intended to serve as organizational units for tenants, not classifications. I'd recommend using tags for the later.
adam commented 2025-12-29 17:24:45 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (Jan 30, 2019):

@jeremystretch:
First of all many thanks for your feedback.
It's a pity that we don't go into it further here.

For your understanding:
There are Tenant and Tenant-Group.
A Tenant may be entered e.g. Pro Site.
A tenant group may also be entered e.g. Pro Site.

A tenant may only be the only one in a tenant group, whereby the name associates tenant group, here are several, therefore also group.

If I follow your logic, then a tenant group is currently no different than another name by a container for a tenant.

So the tenant group is superfluous for me and should not be listed in this form in the software.

Also interesting is the kind of documentation of Netbox itself:
https://netbox.readthedocs.io/en/stable/core-functionality/tenancy/

tenant groups
Tenants can be organized by custom groups. For instance, you might create one group called "Customers" and one called "Acquisitions." The assignment of tenants to groups is optional.

Important here is the last sentence .. tenants is plural.

I see here already in the future the possibility of wanting to add several tenants in a group, because the documentation (see quote above) makes it seem so for an outsider.

Please reopen the ticket again, maybe this feature request can be implemented in the future.

@tb-killa commented on GitHub (Jan 30, 2019): @jeremystretch: First of all many thanks for your feedback. It's a pity that we don't go into it further here. For your understanding: There are Tenant and Tenant-Group. A Tenant may be entered e.g. Pro Site. A tenant group may also be entered e.g. Pro Site. A tenant may only be the only one in a tenant group, whereby the name associates tenant group, here are several, therefore also group. If I follow your logic, then a tenant group is currently no different than another name by a container for a tenant. So the tenant group is superfluous for me and should not be listed in this form in the software. Also interesting is the kind of documentation of Netbox itself: https://netbox.readthedocs.io/en/stable/core-functionality/tenancy/ tenant groups Tenants can be organized by custom groups. For instance, you might create one group called "Customers" and one called "Acquisitions." The assignment of tenants to groups is optional. Important here is the last sentence .. tenants is plural. I see here already in the future the possibility of wanting to add several tenants in a group, because the documentation (see quote above) makes it seem so for an outsider. Please reopen the ticket again, maybe this feature request can be implemented in the future.
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
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#2315
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?