AP.jira.openCreateIssueDialog not validating the "Linked Issues" field when configured as required

XMLWordPrintable

    • Minor

      Issue Summary

      When using the openCreateIssueDialog from the Connect JavaScript API, if the “Linked Issues” field is marked as required but left empty, no error message is displayed and the issue is created. This behaviour differs from the one observed when using the Jira UI, for example, the “Create“ button on the top navigation bar.

      Steps to Reproduce

      1. For a given project define the “Linked Issues” field as required using the Field Configuration option in Project Settings.  
      1. Using the “Create” button in the top navigation bar in the Jira UI, attempt to create an issue for that project leaving the “Linked Issues” field empty;
      1. An error message is displayed below the field and the issue is not created;
      1. Install a connect app that uses the JavaScript API to call the openCreateIssueDialog, for example: 
        AP.jira.openCreateIssueDialog((issues) => {console.log(issues)},
          { 
            pid: projectId,
            issueType: issueTypeId,
            fields: {} 
          }
        ); 

         

      1. Verify that the dialog opens and fill the required information leaving the “Linked Issues” field empty;
      1. Attempt to create the issue.

      Expected Results

      The dialog shown by openCreateIssueDialog should behave the same for the “Linked Issues” field, displaying the error message and stopping the issue from being created, since the field is mandatory.

      Actual Results

      The dialog closes and the issue is created even though the mandatory field “Linked Issues” was empty.

      Workaround

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

            Assignee:
            Pulkit Kejriwal
            Reporter:
            Sherica Ocbania
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: