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

Allow hyperlinking/markdown support in custom field choice sets #10192

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

Originally created by @ghost on GitHub (Sep 6, 2024).

NetBox version

v.4.1.0

Feature type

Data model extension

Proposed functionality

Allow markdown/hyperlink rendering for custom field choice sets.
I'm marking this as 'data model extension' because I imagine some tweaks to the validation will need to happen before saving the values into the database.

When creating a custom field choice set you input the value as choice1:First Choice
It would be a great feature to be able to have markdown supported in the "First Choice" side of the input such that we can turn these values into hyperlinks.

choice1:First Choice
becomes
choice1:[First Choice](https://example.com)

Use case

Adding this ability would allow custom field choice sets to be turned into URL's.
Imagine a scenario where you have a custom field called "Business Units"
You create a custom field choice set that contains all your business unit choices:

widgets:[Widgets](https://netboxurl.com/dcim/sites/?cf_business_unit=widgets)
filters:[Filters](https://netboxurl.com/dcim/sites/?cf_business_unit=filters)

What we would very likely do is craft the URL hyperlink to be a search filter for the value of that custom field so clicking on it from the objects perspective will then take you to a search query for all objects containing that value.
Similar to how you could click on a tag and it would give you all objects with that tag, same concept.

Database changes

Likely some changes here to accept markdown/hyperlinks to be stored in the value of the tablet. Don't know for sure.

External dependencies

None that I can think of.

Originally created by @ghost on GitHub (Sep 6, 2024). ### NetBox version v.4.1.0 ### Feature type Data model extension ### Proposed functionality Allow markdown/hyperlink rendering for custom field choice sets. I'm marking this as 'data model extension' because I imagine some tweaks to the validation will need to happen before saving the values into the database. When creating a custom field choice set you input the value as `choice1:First Choice` It would be a great feature to be able to have markdown supported in the "First Choice" side of the input such that we can turn these values into hyperlinks. `choice1:First Choice` becomes `choice1:[First Choice](https://example.com)` ### Use case Adding this ability would allow custom field choice sets to be turned into URL's. Imagine a scenario where you have a custom field called "Business Units" You create a custom field choice set that contains all your business unit choices: `widgets:[Widgets](https://netboxurl.com/dcim/sites/?cf_business_unit=widgets)` `filters:[Filters](https://netboxurl.com/dcim/sites/?cf_business_unit=filters)` What we would very likely do is craft the URL hyperlink to be a search filter for the value of that custom field so clicking on it from the objects perspective will then take you to a search query for all objects containing that value. Similar to how you could click on a tag and it would give you all objects with that tag, same concept. ### Database changes Likely some changes here to accept markdown/hyperlinks to be stored in the value of the tablet. Don't know for sure. ### External dependencies None that I can think of.
adam added the type: featurenetbox labels 2025-12-29 21:28:03 +01:00
adam closed this issue 2025-12-29 21:28:04 +01:00
adam commented 2025-12-29 21:28:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 10, 2025):

Unfortunately this would be infeasible to implement given the constraints around how custom field choices are implemented: All choices need to be renderable as simple value & label pairings. This might be something to reconsider if we opt to rearchitect custom field choices in the future.

@jeremystretch commented on GitHub (Jan 10, 2025): Unfortunately this would be infeasible to implement given the constraints around how custom field choices are implemented: All choices need to be renderable as simple value & label pairings. This might be something to reconsider if we opt to rearchitect custom field choices in the future.
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 netbox 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#10192
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?