Glenn Matthews

An attempt at consolidating the requirements described in this issue thus far together with some additional requirements identified through internal discussions and documentation: - A dynamic group must automatically reflect...

Although supporting nested filters in general would require a much larger change to filtersets, we think that this specific use case could be addressed by extending the `NaturalKeyOrPKMultipleChoiceFilter` to include...

Something tricky to consider when thinking about this feature is foreign-keys. If an IPAddress "10.1.1.1/24" is associated with "Device A" interface "Eth0" at time X, but later reassigned to "Device...

I think more generally this is a gap for all of our custom field background updates (such as populating default values for a newly created custom field).

I think a "complete" fix here would involve all of the following background task functions in `nautobot.extras.tasks`: - `update_custom_field_choice_data` should create ObjectChange records for each model instance impacted when changing...

Will need to think about how this interacts with job scheduling and approvals - if the job run is no longer atomic, then there will be no ready way for...

For reference: https://github.com/nautobot/nautobot/pull/689 https://github.com/nautobot/nautobot/pull/577

Is "saving" a set of filters, or setting them as per-user defaults for a particular object-list, in scope?

Thanks for the report @jifox. This is a known issue with the way our different demo/sandbox environments are populated with sample data - we're working on getting it addressed.

Should be fixed now.