JMWE issue created on transition isn't linked

[Katherine Japutra]

Hi, 

I set JMWE post-function to one of my workflow with the hope that when it goes through one of the transition, it will automatically clone the issue to another project and link it to the original issue. 

After setting it up, the issue was cloned successfully to the target project with the correct fields BUT it's not linked to the original issue. 

There's also some error 400 in the error log. 

[2019-05-14T13:59:13.624Z] ERROR: mwec/4 on 7542ca2d-26ed-4f4f-b819-ef32d47304a9: Incorrect request: ["We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file."] (accountId=557058:ad944671-a0b9-46e0-8f58-f91911fdee7f, msgType=workflow-error, requestId=a67f334b-80ef-44e4-9e5a-21f0f8deaa0c, issueKey=BR-436, postFunctionId=482279d6-3fff-4c9a-961b-748e7788e530, accountType=atlassian, during=post-function-execution, userName=katherine.japutra, clientUrl=https://flaconi.atlassian.net, postFunction=CreateIssueFunction, clientKey=4ed1c061-2b40-3006-988d-b7aae933133b)
    configuration: {
      "conditionalExecution": false,
      "project": "PIMF",
      "fieldActions": "{\"summary\":{\"action\":\"copy\"}}",
      "copyCommentToNewIssue": false,
      "selectedLinkType": "inward:10000",
      "issuetype": "1",
      "navigateToNewIssue": false,
      "runAsType": "currentUser"
    }
    --
    transition: {
      "workflowId": 372349,
      "from_status": "Verified",
      "transitionId": 171,
      "to_status": "PIM Approved",
      "transitionName": "PIM",
      "workflowName": "Bug Reporting 2.0"
    }
    --
    request: {
      "body": "{\"fields\":{\"project\":{\"key\":\"PIMF\"},\"issuetype\":{\"id\":\"1\"},\"summary\":\"Test issue clone #2\"}}",
      "href": "https://flaconi.atlassian.net/rest/api/2/issue",
      "impersonate": "557058:ad944671-a0b9-46e0-8f58-f91911fdee7f",
      "method": "POST"
    }
    --
    error: {
      "code": 400,
      "name": "Error",
      "fields": "{\"authentication\":5,\"triggering\":6,\"queue\":1,\"delay\":2006,\"execution\":1854}",
      "detail": {
        "errorMessages": [
          "We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file."
        ]
      },
      "codeString": "400",
      "message": "Unexpected response: 400"
    }

Can someone help me troubleshoot this issue? 

[Christian Schneider]

Hi @Katherine Japutra 

Your question is already some days old - did you get a solution? I am having similar issues. The cloned issues is created, in the history of the original issue, there is an entry, that the link was created, but gets deleted emediately.

[David Fischer]

Hi Katherine,

this is really weird, as the error says the issue couldn't be created and yet you're saying it was created anyway. The error would actually explain why the issue link wasn't created (since JMWE received an error from Jira while creating the cloned issue, it didn't go any further), but obviously Jira should not return an error if it actually succeeded.

I would recommend you open a support request with Atlassian Support so they can investigate this error in the Jira Cloud logs.

[Katherine Japutra]

Hi David, thank you for the suggestion. I will do so. 

As you said, it's quite weird for me as well that everything is working except for the linking issue despite the error.

[Alexander Bondarev]

Hi, it seems like problems with required fields on creation.

Check your:

1. screen(creation)

2. required field in field configuration

3. that all required field get value from your post-function,

[Katherine Japutra]

Hi Alexander, thank you for your suggestion. I have done this and unfortunately still no luck. The issue succesfully created but there's no linked issue there.