Current State:

Newly created work item jira fields will not present the selected default response values from the Form Fields if these are added under a Conditional Section, but the section is never shown (condition not met). If we have the section appear, the default responses will populate successfully.

This is how JSM Forms currently function in Cloud. When a conditional section is not visible Forms acts as if that part of the form does not exist (by removing any reference to the form and linked Jira fields).

How to reproduce this behavior:

1. Associate a Form Field to a Jira Field
2. Add a default response to the Form Field
3. Add the form field to a Conditional Section
4. Raise a request with the form, without meeting the section conditional (field is not shown)
5. Default Response value will not be saved into the linked Jira Field

Proposed Future State:

The ideal solution would be that the Form Field default answer always gets carried over into the Jira Field, regardless if the Conditional Section where it resides is shown or not.

Alternatives:

• Remove issue from conditional section.
• Set a default value for the Jira fields in the Request Type Configuration.
• Set the default values after the issue is raise using Automation, for example:
  • "Created work-item" trigger and adding a couple of conditions
  • First to confirm we are on the correct request type
  • Another to validate that the desired fields have no value
  • Passing both checks, then just add the EDIT WORK ITEM action, to modify the desired fields