You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jathanism
changed the title
Bug: Custom Fields cannot filter by name for content_types
Custom Fields cannot filter by name for content_types
Mar 26, 2021
We won't be able to solve for integer PKs for content types because they are built-in, but we can at least hide them. We just need to revise the custom fields relationship to use the same content-types related field subclass we added to support a cleaner UX for working with statuses.
Environment
Steps to Reproduce
extras/custom-fields
bycontent_types=dcim.device
it fails with Observed Behavior below.extras/statuses
bycontent_types=dcim.device
and it worksExpected Behavior
Filter custom fields for any that are tied to
dcim.device
Also, should content-types providers an integer instead of UUID. Not sure if this is due to it being a Django construct primarily.
@jmcgill298 @jvanderaa
Observed Behavior
The text was updated successfully, but these errors were encountered: