Unable to post issue from ReportPortal due to validation issue

kovaku commented 5 years ago

Summary

My team just have deployed jira service to our locally hosted Report Portal cluster, the service is able to communicate with Jira and also it is possible to configure the BTS under the project specific settings. However when I try to post an issue using Report Portal then the following validation issue occurs:

Error occurred: {"error_code":40302,"message":"Impossible interact with external system. [ErrorCollectionstatus=400, errors=customfield_12231=Could not find valid 'id' or 'value' in the Parent Option object., Found in Phase=data was not an array, customfield_15842=Could not find valid 'id' or 'value' in the Parent Option object., errorMessages=[]]"}

The following logs are displayed on the console of the jira service:

com.epam.ta.reportportal.exception.ReportPortalException: Impossible interact with external system. [ErrorCollectionstatus=400, errors=customfield_12231=Could not find valid 'id' or 'value' in the Parent Option object., Found in Phase=data was not an array, customfield_15842=Could not find valid 'id' or 'value' in the Parent Option object., errorMessages=[]]
    at com.epam.reportportal.extension.bugtracking.jira.JiraStrategy.submitTicket(JiraStrategy.java:193) ~[classes!/:na]

The extracted request to BTS:

2019-08-08 07:29:21.440 DEBUG 1 --- [O dispatcher 21] org.apache.http.wire                     : http-outgoing-2 >> "{"fields":{"summary":"Failing test","issuetype":{"id":"1"},"customfield_12231":"ReportPortal autofield","project":{"key":"XXX"},"description":"Failing test\nh3.*Back link to Report Portal:*\n - [Link to defect|http:\/\/XXXXX\/#XXXX\/launches\/all%7Cpage.page=1&page.size=50&page.sort=start_time\/5d39b72eb1d5fc000170060b%7Cpage.page=1&page.size=50&page.sort=start_time&filter.eq.has_childs=false&filter.eq.uniqueId=%5Bengine:junit-jupiter%5D\/%5Bclass:com.xxxxx.xxxxxx.xxxxxxxxxxx.e2e.XXXXXServiceE2E%5D?page.page=1&page.size=50&page.sort=start_time&filter.eq.has_childs=false&filter.eq.uniqueId=%5Bengine:junit-jupiter%5D\/%5Bclass:com.xxxxx.xxxxxx.xxxxxxxxxxx.e2e.XXXXXServiceServiceE2E%5D&log.item=5d39b72eb1d5fc000170060d]\n\n","customfield_15842":"ReportPortal autofield","customfield_11532":"ReportPortal autofield"}}"

After analyzing the related code it turned out that the field that caused validation issue were set to ReportPortal autofield due to the following exception:

2019-08-08 07:29:19.374 ERROR 1 --- [nio-8080-exec-7] c.e.r.e.b.jira.JIRATicketUtils           : null

java.lang.NullPointerException: null
    at com.epam.reportportal.extension.bugtracking.jira.JIRATicketUtils.toIssueInput(JIRATicketUtils.java:157) ~[classes!/:na]
    at com.epam.reportportal.extension.bugtracking.jira.JiraStrategy.submitTicket(JiraStrategy.java:162) [classes!/:na]
    at com.epam.reportportal.extension.bugtracking.BugTrackingController.submitTicket(BugTrackingController.java:74) [commons-bugtracking-4.2.0.jar!/:na]

Notes about the fields that are affected by this issue:

  {
    "id": "customfield_12231",
    "name": "Bug Classification",
    "custom": true,
    "orderable": true,
    "navigable": true,
    "searchable": true,
    "clauseNames": [
      "Bug Classification",
      "cf[12231]"
    ],
    "schema": {
      "type": "option",
      "custom": "com.atlassian.jira.plugin.system.customfieldtypes:select",
      "customId": 12231
    }
  }
"customfield_12231":{"required":true,"schema":{"type":"option","custom":"com.atlassian.jira.plugin.system.customfieldtypes:select","customId":12231},"name":"Bug Classification","hasDefaultValue":true,"operations":["set"],"allowedValues":[{"self":"https://XXXX.XXX/rest/api/2/customFieldOption/14583","value":"New Feature Bug","id":"14583"},{"self":"https://XXXX.XXX/rest/api/2/customFieldOption/14880","value":"Production Bug","id":"14880"},{"self":"https://XXXX.XXX/rest/api/2/customFieldOption/14584","value":"Regression Bug","id":"14584"},{"self":"https://XXXX.XXX/rest/api/2/customFieldOption/14585","value":"Unknown","id":"14585"}]}

  {
    "id": "customfield_15842",
    "name": "Theme",
    "custom": true,
    "orderable": true,
    "navigable": true,
    "searchable": true,
    "clauseNames": [
      "cf[15842]",
      "Theme"
    ],
    "schema": {
      "type": "option",
      "custom": "com.atlassian.jira.plugin.system.customfieldtypes:select",
      "customId": 15842
    }
  },
customfield_15842":{"required":false,"schema":{"type":"option","custom":"com.atlassian.jira.plugin.system.customfieldtypes:select","customId":15842},"name":"Theme","hasDefaultValue":false,"operations":["set"],"allowedValues":[.....

Affected version: Jira Service: 4.3.0 Jira version: JIRA v7.6.4

Could you please support us to find out the rootcause of this issue?