Custom Fields set to read-only are not usable in the filter UI #7024

Closed
opened 2025-12-29 19:48:01 +01:00 by adam · 0 comments
Owner

Originally created by @jasonyates on GitHub (Sep 26, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

3.3.4

Python version

3.9

Steps to Reproduce

  1. Create a custom field & set it's UI visibility to read-only
  2. Visit the relevant model list and attempt to filter based on the custom field

Expected Behavior

Custom field is usable in the Filter UI even when marked read-only.

Observed Behavior

Custom field is blocked from use in a filter. Validated on public demo instance

Screenshot 2022-09-26 at 14 01 58

Originally created by @jasonyates on GitHub (Sep 26, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version 3.3.4 ### Python version 3.9 ### Steps to Reproduce 1. Create a custom field & set it's UI visibility to read-only 2. Visit the relevant model list and attempt to filter based on the custom field ### Expected Behavior Custom field is usable in the Filter UI even when marked read-only. ### Observed Behavior Custom field is blocked from use in a filter. Validated on public demo instance ![Screenshot 2022-09-26 at 14 01 58](https://user-images.githubusercontent.com/242483/192283631-de67ca99-b7fe-407d-a32f-6ed78f456f80.png)
adam added the type: bugstatus: accepted labels 2025-12-29 19:48:02 +01:00
adam closed this issue 2025-12-29 19:48:02 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7024