starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Display Custom Field Tenant Objects Under Tenant Related Objects #11074

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

Originally created by @ChrisRecioHive on GitHub (Apr 23, 2025).

NetBox version

v4.2.6

Feature type

New functionality

Proposed functionality

When a custom field object with the tenant type is added, it should be displayed under Related Objects on the Tenants page.

Use case

Adds the ability to associate tenant relationships with objects that don't natively support them. By using a custom field with the Tenant object, these associations can be created. With this change, those objects will now also appear under Related Objects on the Tenant page.

Database changes

No response

External dependencies

No response

Originally created by @ChrisRecioHive on GitHub (Apr 23, 2025). ### NetBox version v4.2.6 ### Feature type New functionality ### Proposed functionality When a custom field object with the tenant type is added, it should be displayed under Related Objects on the Tenants page. ### Use case Adds the ability to associate tenant relationships with objects that don't natively support them. By using a custom field with the Tenant object, these associations can be created. With this change, those objects will now also appear under Related Objects on the Tenant page. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetboxstatus: backlogcomplexity: high labels 2025-12-29 21:39:53 +01:00
adam commented 2025-12-29 21:39:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 24, 2025):

This is much broader in scope than just tenant assignments: Any such solution would need to support any object or multi-object relationship established via a custom field. While there's some value in implementing this, it may be outweighed by the overhead involved.

@jeremystretch commented on GitHub (Apr 24, 2025): This is much broader in scope than just tenant assignments: Any such solution would need to support _any_ object or multi-object relationship established via a custom field. While there's some value in implementing this, it may be outweighed by the overhead involved.
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 complexity: high netbox status: backlog 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#11074
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?