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

Custom Field Choice Sets - not working #8426

New Issue
Closed
opened 2025-12-29 20:36:34 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:36:34 +01:00
Owner
Copy Link

Originally created by @whtkam on GitHub (Aug 6, 2023).

NetBox version

v3.6-beta1

Python version

3.8

Steps to Reproduce

I tried the new Custom Field Choice Set on the demo instance.

  1. Create Custom Field Choice Sets: "123"
  2. define 3 choices
    1,ONE
    2,TWO
    3,THREE
  3. Create a Custom Field: object type: "dcim | device" name: "123" label:"123" group:"Special" type: "Selection" Choice Set:"123"
  4. Edit custom field: "123" on existing device --> error pops up

Expected Behavior

Select a choice without error

Observed Behavior

Error-Popup

Markdown syntax is supported
2023-08-06 08:29 UTC netbox-beta (v3.6-beta1)
Error Fetching Options for field 'cf_123'

Originally created by @whtkam on GitHub (Aug 6, 2023). ### NetBox version v3.6-beta1 ### Python version 3.8 ### Steps to Reproduce I tried the new Custom Field Choice Set on the demo instance. 1. Create Custom Field Choice Sets: "123" 2. define 3 choices _1,ONE 2,TWO 3,THREE_ 3. Create a Custom Field: object type: "dcim | device" name: "123" label:"123" group:"Special" type: "Selection" Choice Set:"123" 4. Edit custom field: "123" on existing device --> error pops up ### Expected Behavior Select a choice without error ### Observed Behavior Error-Popup _Markdown syntax is supported 2023-08-06 08:29 UTC netbox-beta (v3.6-beta1) Error Fetching Options for field 'cf_123'_
adam added the type: bugbeta labels 2025-12-29 20:36:34 +01:00
adam closed this issue 2025-12-29 20:36:34 +01:00
adam commented 2025-12-29 20:36:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 10, 2023):

I'm not able to reproduce this on the current feature branch. It's likely the bug has already been resolved under #13363.

@jeremystretch commented on GitHub (Aug 10, 2023): I'm not able to reproduce this on the current `feature` branch. It's likely the bug has already been resolved under #13363.
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 beta type: bug
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#8426
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?