Destination Field for form in issue

Destination Issue Fields feature allows you to automatically update your issue field values with the values submitted through a form. So, when a form is added to an issue, and someone submits the form, it enables to transfer of data from the submitted form directly to a Jira issue field that was pre-defined when setting up the form. To enable this functionality, you need to set up the Destination Issue Field in the form element settings beforehand.

Destination Field is available for such types of spreading forms:

  1. Automatic Form Addition. Read more.

  2. Manual Form Addition. Read more.

  3. Form sharing with users out of Jira from an issue. Read more.

  4. Customer Portal Form Addition (JSM). Read more.

    So, this feature doesn’t create new issue based on form responses, but it makes changes in existing issue fields where that form was added.

Characteristics

  1. It is available for such form elements: Single-line text input, Multi-line text input, Dropdown, Multi choice, Checkboxs, Radio buttons, Date, Date and time, Number, and URL.

  2. Data that is transferred from a form elements to an issue field is limited to one-to-one mapping. If you choose the same Destination Issue Field multiple times, only the data from the most recently added form element will be retained.
    The exception to this is the label-type Jira fields.

  3. The Destination Issue Field list reflects all fields from all Jira projects. If you add the form to the issue without the selected field, then the form field value won't be added. So, please select in the DIF list only that Jira issue fields that exist in that issue where you want to add form.

  4. Jira and Custom issue fields. Choose which form element response needs to be mapped in the selected Jira issue field

    1. The availability of Jira and Custom issue fields for relating to form elements depends on the chosen project and issue type.

    2. Jira issue fields and Custom issue fields (example of field type: text, date, number, labels) are available.

    3. To map such Jira issue fields like Select List and similar that have predefined values (example of field type: priority, reporter, dropdown, etc) automatically populate form elements options with the issue field.

    4. Mapping multiple values to Jira fields.

Instruction on how to set up the Destination field for form in issue

  1. Open the Smart Jira Forms add-on. Create a new form or use an existing one. The form must have available form elements for the Destination Field (RF. Characteristics).

    Screenshot 2024-02-15 at 17.31.02.png
  2. Go to the Setting Tab, and click the Destination field button. Relate form elements to the needed Jira or Custom fields where you want to map the form element answers after the form submission.

    Screenshot 2024-02-15 at 17.35.03.png
  3. Save the form and spread it conveniently (manual add, auto add, on Customer Portal, or shared externally from the issue). Once the respondent fills out the form and submits it, form elements values will automatically map to the selected Jira field. In the next gif, it is shown how it happens.

Instruction on how to set up the predefined issue field in the Destination field

  1. Open the Smart Jira Forms add-on. Create a new form or use an existing one.

  2. On available for Populate options from the issue field element (RF. Characteristics) click on the Edit icon, and press the Populate options from the issue field. Choose what values of the issue field you want to populate in the form element options.

  3. Now because of the settings done above you can choose the issue field in the Destination field. Choose it and apply form elements settings.

The Destination Issue Field list reflects all fields from all Jira projects. If you add the form to the issue without the selected field, then the form field value won't be added. So, please select in the DIF list only that Jira issue fields that exist in that issue where you want to add form.

  1. Save the form and spread it conveniently (manual add, auto add, on Customer Portal, or shared externally from the issue). After form submission, the form element value will automatically map to the Jira field in the existing issue (where the form is added). In the next gif, it is shown how it happens.