JIRA Spoke: Methods failing with 404

[Jonathan Demeul]

Good afternoon,

We have recently moved from JIRA Server to JIRA Cloud and I'm rebuilding our old integration to work with the JIRA Cloud setup.

I followed all the instructions to the letter and succeeded in getting my OAuth token from JIRA. So far so good. However, all the actions from the JIRA spoke are not working and throwing errors.

This is one example for the Lookup Issue action (I redacted my cloud id):

Method failed: (/ex/jira/REDACTED/rest/api/2/issue/QRUNIT-301) with code: 404

{"timestamp":"2023-06-29T11:40:34.971775Z","status":404,"error":"Not Found","message":"No message available","path":"/ex/jira/REDACTED/rest/api/2/issue/QRUNIT-301"} 

[Mathieu Lepoutr]

Hi Jonathan

It seems that the integration is encountering a "404 Not Found" error when performing the Lookup Issue action in JIRA Cloud. It seems that the specified issue, "QRUNIT-301," cannot be found in JIRA.

To troubleshoot the issue, check the following:

1. Ensure the issue key is correct.
2. Verify that the user associated with the OAuth token has sufficient permissions.
3. Confirm the accuracy of the REST API endpoint URL.

If the issue persists, consider using Exalate as an option. I have been using it for quite a while. Exalate is a third-party integration platform that specializes in synchronizing data between JIRA instances.

[S_bastien Lavoi]

Hello Jonathan.  We have the same issue.  Did you managed to find the solution?

[psoni7]

Hi Jonathan, 

Is this issue resolved; can you help me with the solution.

I am facing the same issue.

Regards,

Priyanka Soni