Issue Summary

An HTTP 500 error is thrown referring to an exception in the OOFunctionsSql.asp file when end-users attempt to import Epics.

Steps to Reproduce

• Unable to reproduce in Labs

Expected Results

• The work items get imported successfully

Actual Results

• An HTTP 500 error is thrown and the corresponding exception is captured in Splunk:

  { [-]
     ASP_function: Error.asp
     ErrorId: 25024
     PageName: Import
     correlationid: UyvyMIUUN+NMVrZUwNPgptOedTkXUOECs78F0g6Bw5Q=
     customer_db: <CUSTOMER_NAME>
     error_aspcode:
     error_aspdescription:
     error_category: Microsoft SQL Server Native Client 11.0
     error_column: -1
     error_description: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
     error_file: /OOFunctionsSql.asp
     error_line: 289
     error_number: -2147467259
     error_source:
     log_type: exception
     logfrom_location: Website-ASP
     timestamp: 2023-03-07T17:16:04.335000-05:00
     url: https://<instance_name>.jiraalign.com:443/ImportObjects.asp
     urlverb: POST
     user: <USER_ID>
     version: 10.117.2.27714
  }

Workaround

End-users may use Jira Align REST API to import/update work items. There are methods available for either creating new work items (POST) or updating pre-existing ones (PUT (full updates, work item replacement) or PATCH (partial updates)).

Please review the Help Center's API 2.0 resource hub page for details on Jira Align REST APIs.

Atlassian Support is unable to provide customers with "ready-to-use scripts". Support can, however, assist customers with crafting their Jira Align REST API calls themselves with the proper payloads, based on their particular needs.
Please raise a Support ticket should further assistance be needed.