Setting a single select field to "none" for a dynamic field in a Connect App does not change the data

XMLWordPrintable

    • Severity 2 - Major

      Issue Summary

      Setting a single select field to "none" for a dynamic field in a Connect App does not change the data.
       

      Steps to Reproduce

      1. Create custom issue field using dynamic module rest api. Using POST method to /rest/atlassian-connect/1/app/module/dynamic, send:
        "jiraIssueFields":[
          {
            "key":"team-issue-field",
            "name":{
              "value":"Team"
            },
            "description":{
              "value":"Team tied to issue"
            },
            "type":"single_select",
            "extractions":[
              {
                "path":"category",
                "type":"string",
                "name":"category"
              }
            ]
          }
        ]
        
      1. Add option to newly created custom issue field. Using create api for connect app following this rest api: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options--apps-/#api-rest-api-3-field-fieldkey-option-post
      2. Select one option in the newly created custom issue field in jira project issue:
      3. Try to deselect option, set to none - it will work visually
      4. Refresh the page, to check if the field value has been saved.

      Expected Results

      The option has been set to none, as was shown in the UI.

      Actual Results

      The option has returned to the set value, in disagreement with the UI.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

            Assignee:
            Unassigned
            Reporter:
            devpartisan
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: