Jira API call received 400 response, but created issue anyway

[Chris Solgat]

We have an external process that allows a user to create a JIRA issue through the rest/API.  It also receives the response code to let the user know that the issue was created.  We have run into a scenario where the API call is sending a 400 response code back to the user, so the user thinks the issue wasn't created.  They are then creating another issue, which gets the proper response back.  The problem is, the first issue was actually created, so we are getting duplicate issues.  Anyone have any ideas why the issue would still be created when the response is a 400 code?

[Volodymyr Krupach]

As per doc: STATUS 400 Returned if the input is invalid (e.g. missing required fields, invalid field values, and so forth).

Does the second (i.e. successful) request pass the same JSON?

[Chris Solgat]

From what I could see in the logs, yes. I believe they are using some sort of application type front end, so it should be pretty consistent.