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

Incorrect raw value for "loose" custom field filter logic #4300

New Issue
Closed
opened 2025-12-29 18:34:31 +01:00 by adam · 0 comments
adam commented 2025-12-29 18:34:31 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Nov 24, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.9
  • NetBox version: 2.9.9

Steps to Reproduce

  1. Create a custom field with its filter logic set to "loose"
  2. Inspect the column's value in the database table (extras_customfield.filter_logic)

Expected Behavior

The value should read "loose".

Observed Behavior

The value reads "integer".

This is due to an error in database migration 0029_3569_customfield_fields under the extras app, which incorrectly converts the old numeric representation to the slug value "integer" instead of "loose". (This was due to a copy/paste error when constructing the migration.)

It's worth noting that this error doesn't actually inhibit functionality. However, with REST API support being introduced for custom fields in v2.10 (#5274), the value needs to be corrected.

Originally created by @jeremystretch on GitHub (Nov 24, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.9 * NetBox version: 2.9.9 ### Steps to Reproduce 1. Create a custom field with its filter logic set to "loose" 2. Inspect the column's value in the database table (`extras_customfield.filter_logic`) ### Expected Behavior The value should read "loose". ### Observed Behavior The value reads "integer". This is due to an error in database migration `0029_3569_customfield_fields` under the extras app, which incorrectly converts the old numeric representation to the slug value "integer" instead of "loose". (This was due to a copy/paste error when constructing the migration.) It's worth noting that this error doesn't actually inhibit functionality. However, with REST API support being introduced for custom fields in v2.10 (#5274), the value needs to be corrected.
adam added the type: bugstatus: accepted labels 2025-12-29 18:34:31 +01:00
adam closed this issue 2025-12-29 18:34:31 +01:00
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 status: accepted 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#4300
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?