Proforma does not sync the default value of a custom field from a required question, if that question is hidden by a section

XMLWordPrintable

      Issue

      Proforma does not set a custom field to the default value configured in the "Radio button" question configured in the form, if that question is hidden by a section.

      Steps to replicate

      Scenario 1 - JSM Project with a default value set in the Request Type configuration

      1. Create a JSM (Jira Service Management) Project
      2. Configure a new select list custom field, with 3 options
        • Option 1
        • Option 2
        • Option 3
      3. Add this custom field to all the screens of the JSM project
      4. Configure a Request Type in the JSM project to include this custom field, and set it as required with "Option 2" as the default value
      5. Configure a new form as follows:
        • Add a radio button with Show and Hide as options
        • Add a section with "Show section" set to "Conditionally", and which will depend on the value of the Show/Hide question located above
        • Add a radio button that is linked to the Select Custom Field created in the first step. Make this question required ("Response Required") and set "Option 3" as the "default answer"
      6. Create a new request from the customer portal and select the request type that the form is linked with
      7. Create the request by either not selecting show neither hide, or by selecting "hide"

      Scenario 1 - Expected behavior

      Even though the radio button that is linked to the custom field is not showing on the customer portal we would expect the Select List Custom Field to be set to the default value specified in the form.

      We would also expect the request creation to fail, since there is a required question configured in the form (even though it is hidden).

      Scenario 1 - Actual behavior

      • The request is created
      • The Select List Custom Field is set to the default value configured in the Request Type configuration, and not to the default value configured in the "Radio button" question configured in the form

      Scenario 2 - JSW Project, with a default value set in the Custom Field Context configuration

      1. Create a JSW (Jira Software) Project
      2. Configure a new select list custom field:
        • with 3 options
          • Option 1
          • Option 2
          • Option 3
        • With "Option 2" as the default value
      3. Add this custom field to all the screens of the JSW project
      4. Configure a new form as follows:
        • Add a radio button with Show and Hide as options
        • Add a section with "Show section" set to "Conditionally", and which will depend on the value of the Show/Hide question located above
        • Add a radio button that is linked to the Select Custom Field created in the first step. Make this question required ("Response Required") and set "Option 3" as the "default answer"
      5. Go to ⚙ > Manage Apps > PROFORMA > Configuration
        • Enable Issue Forms (the Issue Forms option will start showing in the Jira Top Bar Menu)
      6. Click on Issue Forms from the Top bar menu, and search for the form from the JSW project
      7. Create the Jira issue by either not selecting show neither hide, or by selecting "hide"

      Scenario 2 - Expected behavior

      Even though the radio button that is linked to the custom field is not showing on the issue form, we would expect the Select List Custom Field to be set to the default value specified in the form.

      Scenario 2 - Actual behavior

      The custom field is not set to any value (not even the default value configured in the Custom Field Context configuration).

      Important note

      Let's assume that the customer selects the "show" option that is meant to show the Radio Button linked to the custom field (in the Form configuration):

      In this case, once the request is created, the default value configured in the Request Type configuration will be ignored, and the value selected in the radio button (linked to the custom field) will be set in the custom field (Option 3 in the example below):

      Suggestion for this Feature Request

      Set the Custom Field to the default value specified in the form, regardless if the question is hidden or not by a section.

        1. ActualResults.png
          ActualResults.png
          88 kB
        2. Note1.png
          Note1.png
          75 kB
        3. Note2.png
          Note2.png
          109 kB
        4. Step1.png
          Step1.png
          148 kB
        5. Step2.png
          Step2.png
          141 kB
        6. Step3.png
          Step3.png
          93 kB
        7. Step4.png
          Step4.png
          147 kB
        8. Step5.png
          Step5.png
          69 kB
        9. Step6.png
          Step6.png
          65 kB
        10. Step7.png
          Step7.png
          57 kB
        11. Step8.png
          Step8.png
          39 kB

            Assignee:
            Unassigned
            Reporter:
            Julien Rey (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: