Allow a Field to be Designated as Context for Search #270
Description
Plugin Version
0.4.0
Proposed functionality
When editing an object of a built-in model (such as a device), a number of fields allow not the only the primary name of the field to be viewed and searched against, but also a specific field designated as context. For example, on dcim.Device, the device_type field also allows viewing and searching against the manufacturer, and the virtual_chassis field allows viewing searching against the VC master. This request proposes that similar context be made available for custom objects. Not sure if this would have to be done using the comments field, or if it would be possible to allow users to designate a COTF for this use.
Use case
One key use case of custom objects is to relate them to built-in models using custom fields. This works well when COs have a field that will always be uniquely identifiable. However, in my use case, I'm trying to define static routes that exist across many different devices. From the perspective of selecting the routes from a custom field, there currently isn't a good way to visibly identify which routes belong to which device or what they are used for. I'm sure there are other use cases that would benefit from having this extra context available as well.
External dependencies
N/A