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

Automatic data completion #5455

New Issue
Closed
opened 2025-12-29 19:28:16 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:28:16 +01:00
Owner
Copy Link

Originally created by @rfl64 on GitHub (Oct 1, 2021).

NetBox version

v3.0.4

Feature type

New functionality

Proposed functionality

Would be possible to enter Tenant and related data when a Site is selected for a new device?

Use case

When I enter a new device I always must select Site, Tenant, Tenant Group, etc

I suppose a Site belongs to a Tenant, then selecting Site should be enought.

thanks

Database changes

No response

External dependencies

No response

Originally created by @rfl64 on GitHub (Oct 1, 2021). ### NetBox version v3.0.4 ### Feature type New functionality ### Proposed functionality Would be possible to enter Tenant and related data when a Site is selected for a new device? ### Use case When I enter a new device I always must select Site, Tenant, Tenant Group, etc I suppose a Site belongs to a Tenant, then selecting Site should be enought. thanks ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:28:16 +01:00
adam closed this issue 2025-12-29 19:28:16 +01:00
adam commented 2025-12-29 19:28:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 1, 2021):

Would be possible to enter Tenant and related data when a Site is selected for a new device?

I understand your reasoning, however this requires assuming the user's intent. It's perfectly valid to have a device and its site assigned to different tenants, so we can't automatically make that assumption on behalf of the user.

@jeremystretch commented on GitHub (Oct 1, 2021): > Would be possible to enter Tenant and related data when a Site is selected for a new device? I understand your reasoning, however this requires assuming the user's intent. It's perfectly valid to have a device and its site assigned to different tenants, so we can't automatically make that assumption on behalf of the user.
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 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#5455
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?