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

Contact Objects for Prefixes #6119

New Issue
Closed
opened 2025-12-29 19:36:58 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:36:58 +01:00
Owner
Copy Link

Originally created by @tioan on GitHub (Feb 18, 2022).

NetBox version

3.1.8

Feature type

Data model extension

Proposed functionality

It should be possible to assign a Contact Objects to a prefix.
#8087 is unfortunately not a solution, because we have to document different contact persons per prefixes within a tenant.

Use case

The documentation of contact persons for individual prefixes.

Database changes

No response

External dependencies

No response

Originally created by @tioan on GitHub (Feb 18, 2022). ### NetBox version 3.1.8 ### Feature type Data model extension ### Proposed functionality It should be possible to assign a Contact Objects to a prefix. #8087 is unfortunately not a solution, because we have to document different contact persons per prefixes within a tenant. ### Use case The documentation of contact persons for individual prefixes. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:36:58 +01:00
adam closed this issue 2025-12-29 19:36:58 +01:00
adam commented 2025-12-29 19:36:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 22, 2022):

It should be possible to assign a Contact Objects to a prefix.

Why? It seems very uncommon that you would need to associate a particular prefix with a particular individual. NetBox already provides tenancy assignment for prefixes, which seems much more apt.

@jeremystretch commented on GitHub (Feb 22, 2022): > It should be possible to assign a Contact Objects to a prefix. Why? It seems very uncommon that you would need to associate a particular prefix with a particular individual. NetBox already provides tenancy assignment for prefixes, which seems much more apt.
adam commented 2025-12-29 19:36:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 6, 2022):

I'm going to close this as there's been no further explanation of the use case.

@jeremystretch commented on GitHub (Apr 6, 2022): I'm going to close this as there's been no further explanation of the use case.
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#6119
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?