Skip to content
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

Parent Child Tenant Hierarchy #12727

Closed
wirestar opened this issue May 25, 2023 · 5 comments
Closed

Parent Child Tenant Hierarchy #12727

wirestar opened this issue May 25, 2023 · 5 comments
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: revisions needed This issue requires additional information to be actionable type: feature Introduction of new functionality to the application

Comments

@wirestar
Copy link

NetBox version

3.4.3

Feature type

New functionality

Proposed functionality

We would like to add the parent field on tenant creation, and be able to select another tenant as the parent.

Other records, like regions, and locations have this similar parent field that "can be nested recursively to construct a hierarchy" functionality.

Use case

A tenant is considered a customer for us. Our accounting and billing systems allow for parent and child relationships for customers.
I am aware of tenant groups, and those have the parent field to select another group, but this is not quite the same. This is a grouping of tenants, but doesn't show the hierarchy or relationship of tenants.

Database changes

Unknown

External dependencies

Unknown

@wirestar wirestar added the type: feature Introduction of new functionality to the application label May 25, 2023
@abhi1693
Copy link
Member

abhi1693 commented May 26, 2023

I'm not sure if this will be accepted but this will be blocked until #12552 is resolved.

@abhi1693 abhi1693 added the status: blocked Another issue or external requirement is preventing implementation label May 26, 2023
@jeremystretch
Copy link
Member

You haven't explained your use case. NetBox provides for contact assignments where separate points of contact must be tracked within a tenant. Can you provide an example where this would not be sufficient?

@jeremystretch jeremystretch added status: revisions needed This issue requires additional information to be actionable and removed status: blocked Another issue or external requirement is preventing implementation labels May 26, 2023
@wirestar
Copy link
Author

@jeremystretch I am not understanding how contact assignments would show the hierarchies and relationships between tenants? Can you explain as I might be overlooking something?

"A contact represent an individual" person whereas "tenants are used to represent individual customers or internal departments within an organization" according to the NetBox documentation.

Most of the large CRMs like Salesforce or ERPs have the concept of a tenant being a customer, and an employee working at the customer being a contact linked to that customer or vendor.

Our use case would be to have our existing CRMs and ERPs integrated to NetBox. So when a parent customer is created in the CRM or ERP, it syncs to NetBox using the API. If a child record is created, it pushes that as well also showing the parent as it does in the CRM or ERP.

Some areas of NetBox support this concept today such as regions and locations, but then other sections don't but allow a parent to be define but instead have groups (tenants and sites for example). Why is there a difference between these object types?

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Aug 30, 2023
@github-actions
Copy link
Contributor

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 29, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: revisions needed This issue requires additional information to be actionable type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants