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

Rack Reservations - Custom Field REST API filtering not working #4512

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

Originally created by @anttof on GitHub (Jan 29, 2021).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.7.9
  • NetBox version: 2.10.4

Steps to Reproduce

  1. Create Custom Field (tried text, boolean, integer so far) - Apply field on rack-reservations.
  2. Create rack-reservation and fill in created custom-field.
  3. Use "?cf_customfieldname=value" REST API filter to filter rack-reservations
  4. Example:

Expected Behavior

Only rack-reservations matching custom-field rest api filter should be matched and displayed.

Observed Behavior

All rack-reservations are displayed with the rest api filter applied. Including those not matching the filter.

Originally created by @anttof on GitHub (Jan 29, 2021). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.7.9 * NetBox version: 2.10.4 ### Steps to Reproduce 1. Create Custom Field (tried text, boolean, integer so far) - Apply field on rack-reservations. 2. Create rack-reservation and fill in created custom-field. 3. Use "?cf_customfieldname=value" REST API filter to filter rack-reservations 4. Example: * https://netbox.net/api/dcim/rack-reservations/?cf_service_id=123456 <-- Displays all rack-reservations, including those with other cf "service_id" than "123456" * https://netbox.net/api/dcim/devices/?cf_service_id=123456 <-- Works correctly and displays only devices with cf "service_id" set to "123456" <!-- What did you expect to happen? --> ### Expected Behavior Only rack-reservations matching custom-field rest api filter should be matched and displayed. <!-- What happened instead? --> ### Observed Behavior All rack-reservations are displayed with the rest api filter applied. Including those not matching the filter.
adam added the type: bugstatus: accepted labels 2025-12-29 18:36:51 +01:00
adam closed this issue 2025-12-29 18:36:51 +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#4512
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?