Form fields can be linked to Jira fields (standard or custom), making the data available for reports and JQL queries, for triggering automation, including in scripts or organizing a queue. The value entered in the form field will populate the Jira field and vice versa.
If a form has been Submitted, then the linked field on the form will not change, unless the form gets reopened. This allows ProForma to be used as a system of record. You can also Lock the form to further restrict access.
Click here to see a tutorial. You can change the language for the video by clicking on the Language icon in the upper right corner.
Making a Field Available for Linking
Currently, ProForma uses the most recently created issue as the template issue type to determine what fields can be linked to. If the field you wish to link to is not listed in the dropdown, temporarily create an issue of the desired issue type. Then return immediately to the form builder and edit your form template. The desired field should now be included as option to link to. Do not delete the issue you created, as this can cause the fields to become unlinked.
Note that while this method should work in most cases, it will not work for the following field types:
Attachment - See workaround
Custom cascading choice lists (single or multiple) - See workaround
Custom next-gen people fields
Due date (Server and Data Center) - See workaround
Labels - See workaround
**Field created by other apps (ProForma does not currently integrate with DEISER ProFields. Integration with Insight fields is in development.)
Note that we are working to improve how ProForma recognizes available fields and to make it possible to link to all field types.
**ProForma may or may not be able to link to fields created by other Jira apps. If there is a third-party field that you would like to be able to link to, please let us know.
Limitations of Linked User Lookup Fields
Note that a ProForma user picker field that is linked to a Jira user picker field, will not reflect any constraints (filtering to specific groups) that exist on the Jira field). This limitation will be addressed in future development.