Move Issues To Sprint API takes an exceptionally long time

[micahmonticello]

When using this API to directly access JIRA, it takes between 20 seconds and 3 minutes to respond. The action is successful and the issues are moved, but the latency is way too long. A consistent problem for us in both UI and Postman. Does anyone know why it would take this long? Please let me know any details related to this issue. Thanks.

PS Other requests respond in normal time.

[Earl McCutcheon]

Hello Micah,

I did some testing on this and the EndPoint is Posting without issue when i'm doing this locally using curl and postman:

curl -D- -u user -X POST --data "{\"issues\": [\"ASDF-9\"]}" -H "Content-Type: application/json" "http://<BASE_URL>/jira760/rest/agile/1.0/sprint/37/issue"

 And looking at this I would guess that this is network related, somethinf in the firewall or Proxy causing a delay.

To support this I found the following Issue on the GitHub API with a similar Delays in POST and PUT that the user was able to track back to a proxy issue:

- https://github.com/expressjs/express/issues/3235

devilgags commented on Mar 6, 2017
Finally figured it out... The enterprise proxy was causing the request to stall. Everything is working fine now.
Thanks @wesleytodd @dougwilson @victor0801x for your quick support. 👍 Hence, closing the issue.

I would recommend bypassing your Proxy as a first step to see if the response times are increased as a result.

Regards,
Earl