Issue:
We're trying to promote the adoption of the issues tool with field users. To minimize the effort it takes to enter in new issues we are templating out the most common issue types so field supervisors can add them on the fly. Issue templates can really save time, but they are optional, and it takes additional clicks for the user to create an issue based on a template.
Suggestion:
Allow admins to mandate the use of an issue template for specific issue types.
For example: A user drops a pin for a "Quality" issue on the plans.
Current functionality would need them to select a template in the "Start from Template" field.
Suggested functionality would be to automatically utilize the Quality issue template, if and only if the admin has marked that Quality issue template as mandatory.
Benefit:
Common complaint received from field staff is that it takes too much administrative effort to get work done in Forma, and they aren't wrong. Templating and pre-population is our strategy to address that. The easier it is for field staff to utilize Forma, the better our adoption & utilization will be, and the more useful the Forma platform will be in helping complete construction work well.
