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

Allow LinkStatusChoices to be customised via FIELD_CHOICES #10870

New Issue
Closed
opened 2025-12-29 21:37:02 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:37:02 +01:00
Owner
Copy Link

Originally created by @cruse1977 on GitHub (Mar 11, 2025).

NetBox version

v4.2.5

Feature type

New functionality

Proposed functionality

Many NetBox choices are permitted to be modified via FIELD_CHOICES config parameters, however Link Status is not, adding a key (eg: Link.status) to this would allow users to add or change values.

Use case

Examples I've seen of custom status fields include 'missing' and 'damaged'

Database changes

n/a

External dependencies

n/a

Originally created by @cruse1977 on GitHub (Mar 11, 2025). ### NetBox version v4.2.5 ### Feature type New functionality ### Proposed functionality Many NetBox choices are permitted to be modified via FIELD_CHOICES config parameters, however Link Status is not, adding a key (eg: Link.status) to this would allow users to add or change values. ### Use case Examples I've seen of custom status fields include 'missing' and 'damaged' ### Database changes n/a ### External dependencies n/a
adam added the type: feature label 2025-12-29 21:37:02 +01:00
adam closed this issue 2025-12-29 21:37:02 +01:00
adam commented 2025-12-29 21:37:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 14, 2025):

Link status choices are not customizable because these values have significance in cable path calculations. For instance, a cable path is considered complete only if the status of each cable within the path is connected:

f286449284/netbox/dcim/models/cables.py (L599-L602)

If a user were to remove or rename this status, the entire cable tracing system would break.

@jeremystretch commented on GitHub (Mar 14, 2025): Link status choices are not customizable because these values have significance in cable path calculations. For instance, a cable path is considered complete only if the status of each cable within the path is `connected`: https://github.com/netbox-community/netbox/blob/f2864492844b6825de84e0b50679a6b29cd5b285/netbox/dcim/models/cables.py#L599-L602 If a user were to remove or rename this status, the entire cable tracing system would break.
adam commented 2025-12-29 21:37:03 +01:00
Author
Owner
Copy Link

@cruse1977 commented on GitHub (Mar 14, 2025):

Thanks Jeremy, I had a quick look through and obvious missed this one - appreciate the explainer.

@cruse1977 commented on GitHub (Mar 14, 2025): Thanks Jeremy, I had a quick look through and obvious missed this one - appreciate the explainer.
adam commented 2025-12-29 21:37:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 14, 2025):

FWIW we could add additional statuses, such as those you list above, as built-in choices.

@jeremystretch commented on GitHub (Mar 14, 2025): FWIW we could add additional statuses, such as those you list above, as built-in choices.
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#10870
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?