Extending filtering of date custom field type

[jakubkrysl]

As ...

Dan - Data Owner

I want ...

to filter data by before/after custom field of type date

So that ...

I can find all devices whose warranty will expire after certain date. Warranty is only one of 5 dates we have as custom field.

I know this is done when...

• Using loose filtering condition allows for these extensive filters and does not behave same way as exact
  • loose and exact filtering of custom fields is an old concept that we will be moving away from.
• I am able to filter custom fields by before/after some date via API
• I am able to filter custom fields by before/after some date via changing parameter in URL
• (further discussion needed) I am able to filter custom fields by before/after some date via GUI

Date/time custom fields should use the same lookup expression filters as concrete fields.

Optional - Feature groups this request pertains to.

• Automation
• Circuits
• DCIM
• IPAM
• Misc (including Data Sources)
• Organization
• Plugins (and other Extensibility)
• Security (Secrets, etc)
• Image Management
• UI/UX
• Documentation
• Other (not directly a platform feature)

Database Changes

None most probably

External Dependencies

No response

[glennmatthews]

Thanks for the request! In general it seems like it should be desirable and possible to extend the custom-field filtering support so that any given custom field supports the appropriate filtering operators that a non-custom field of the same type would have, so a "date" custom field would support cf_<name>__gt, cf_<name>__gte, etc. It looks like it might be possible to take some inspiration from similar work that was done under netbox-community/netbox#7678.

[glennmatthews]

Possible duplicate of #1288.

[jathanism]

IMO the range filter should be implemented on Date filter types across the board!

[bryanculver]

Closed with #2126