Gary Snider

It might be a good idea to just standardize the database fields. For example, if it's a speed (circuit or interface speed), standardize on bits per second. If it's a...

API fields should no longer be an issue in 2.x but filters are still missing. API may still be missing these fields in 1.6.

This should be generally resolved by #2782 but we should have some testing around Namespace DynamicGroups and some defensive coding around this particular situation where `filter_form is None`

Moving this to draft until I can figure out why it's flakey

It probably doesn't make sense to make this a system job yet since we still don't support running jobs without a user (the ORM case here). We should be able...

# Design meeting notes - Create new `ComponentModel` for `ModuleBay` and `ComponentTemplateModel` for `ModuleBayTemplate` for placing modules on devices. Both models contain a `CharField` for `position` - Create `ModuleType` for...

- Lets also consider the case where Nautobot is used as an inventory for modules that may not yet be installed. So I may want to instantiate a bunch of...

This is implemented with the [`DryRunVar`](https://docs.nautobot.com/projects/core/en/next/development/jobs/#dryrunvar) in 2.0

## Notes from design review Worst case scenario: 700 device dynamic groups with device type + location filters. The location filter is expensive due to the recursive CTE. Thinking about...

Also add a generic test to look for this and open an issue to have this added as a rule in pylint-nautobot