The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Problem with using Rest Tempo API
Hi,
After a lot of trying I come to you.
I want to create an atlassian-connect plugin for Jira Cloud which requires using Tempo's Rest API in order to retrieve account information and especially monthly budgets.
For that I followed the use of your documentation concerning the API for Jira Cloud.
I have correctly configured the token from OAuth 2.0 and I have also tried with the user token.
When I want to send the request with software such as Postman using Authorization by Bearer. This is not a problem.
But when I integrate it into my plugin I have 3 different types of errors depending on how I want to integrate it.
1 - If I use fetch in Javascript I have:
"GET net::ERR_ABORTED 401 (Unauthorized)"
2 - If I use Ajax I have the CORS error:
"blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource."
3 - If I use AP.request which is recommended by (Jira) I have the CORS error:
"blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource."
How to fix the problem? Where can I find documentation for concrete use of the Rest Tempo API?
Best regards,
Julien.
1 comment
Comments for this post are closed
Community moderators have prevented the ability to post new comments.