Legacy form data format
Manipulating ProForma data directly via the Jira API is not supported
Although reading (or GETTING) form data via this API is safe, be very careful when writing (or PUTTING) data back into an issue's entity property, especially in a production environment. There are 2 big risks that are involved with this.
The structure of the JSON output is not set in stone and is subject to change. In fact, it is likely to change in the near future as we make changes to the current form system.
Corrupted forms. If a mistake is made, it is very easy to corrupt, alter or destroy data which has been entered into a form. Manipulating form state might even make it so forms attached to an issue won't load at all. If this happens, the Forms widget on the issue will show an endlessly spinning loader, and it will be unusable.
Reading JSON Output
JSON output of from an individual ProForma form (accessed via the proforma.forms.i1 property) might look similar to the following:
Here are some points to remember when looking at the JSON output.
The data schema version is stored in the '{{schemaVersion}}' property.
Any form created with recent versions of ProForma should have the number 5 in this property.
Questions are stored in order in the '{{questions}}' property.
Each question has an ID in its '{{id}}' property which is unique within the form and does not change. All copies of the same form will share the same set of IDs.
Each question has a type stored in its '{{t}}' property. See below for a list of the types.
Text questions store their answer in the question '{{text}}' property.
Date questions store their answer in the question '{{date}}' property.
Time questions store their answer in the question '{{time}}' property.
Choice questions store their answer in the choices listed on the question '{{choices}}' property. Choices which have been selected will have their property {{selected}} set to true. If the property {{selected}} is not present or is false then that choice is not selected. The question types are:
Question Types
This is how each question type is represented.
h1: section heading (read-only heading)
in: information (read-only HTML)
ts: short text
tl: long text
pg: paragraph text
da: date
dt: date and time
ti: time
cd: choice dropdown (select)
cs: choice single (radio)
cm: choice multiple (checkbox)
no: number
um: user picker (multiple)
us: user picker (single)
Writing Data To A Form
It is possible to use a HTTP PUT request to write information back to the that same REST endpoint. This can allow users to alter the data entered into form fields (however not the form structure), or manipulate the state of a form. For example, a script to reopen a form can be achieved by removing the "submitted' : "true" entry in the form JSON and writing the result back to the issue.
However, as mentioned in the warning above, be very careful when doing this an employ proper error handling and anticipate edge cases. Writing data back to an issue in the wrong way can corrupt data or make forms not work at all on a specific Jira issue.