MVP Planning features

Problem/Motivation

One use-case of templates is in conjunction with plans. Templates allow users to define a consistent structure for creating and editing many records (mostly logs) that should be managed under a common management plan. The same templates can be re-used year after year or even on within the same year when applied to different fields.

For an MVP we need to be able to configure a plan to use a record template. It also should be possible to set defaults/overrides for specific fields on the template, most commonly a log asset reference and log timestamp. This way a generic template can be designed for re-use, but still be customized with further defaults once added to a plan.

Steps to reproduce

N/A

Proposed resolution

Remaining tasks

Implement
Test
Identify next steps

User interface changes

Template plans + templates

API changes

None

Data model changes

Fields/field type to support templates on plans