Allow flexibility when populating hidden fields.

[David.Byrne@…]

From what I can tell, hidden fields can be cleared (when hidden) or populated with a copy of another field (using the copy_from), or populated with a default value from the user preferences. We have a case where it would be nice to populate this field based on the contents of another field. In our use case, we have a ticket type that is handled by including a check-off list in the description of the ticket. This list is populated into the description field by setting the description to something like:

[[TemplInclude(Forms/FORMNAME)]]

The FORMNAME part of the field is a pull-down field that the user selects. I would envision that a hidden fields value would be set by something like

description.value_when_hidden = '[[Include(Forms/$formname)]]'

where formname is the field name on the ticket being copied over. There may be other uses for this as well. It would be a way to populate a ticket field directly from other data elements that are in the ticket.

[Ryan J Ollos]

Closing old ticket as out-of-scope for this plugin. Will reconsider if someone makes the request.