Major changes to Connect REST APIs are coming to improve user privacy

Jira Development Jira Cloud
, , ,
1

In addition to the API changes that have been announced for Jira and Confluence, we’re also making changes to Connect APIs.

A summary of the changes with tickets to follow has been posted to both the Jira and Confluence REST API docs:

https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement-connect/

6 Likes
3

I try to delete project with rest API, I get 500 error even though it seems that the project does get deleted.

Using oauth with Bearer token, I’m trying to delete a project via the rest api like this:

curl -X DELETE \
  https://api.atlassian.com/ex/jira/.../rest/api/3/project/11349 \
  -H 'authorization: Bearer ... ' \
  -H 'cache-control: no-cache'

API returns 500 error like this:


HTTP 500 https://api.atlassian.com/ex/jira/.../rest/api/3/project/11349
Read timed out

response_headers = {
    'X-XSS-Protection': '1; mode=block',
    'X-Content-Type-Options': 'nosniff',
    'X-Application-Context': 'Stargate:prod,prod-east:8080',
    'transfer-encoding': 'chunked',
    'Strict-Transport-Security': 'max-age=315360000; includeSubDomains; preload',
    'X-Failure-Category': 'SOCKET_TIMEOUT',
    'Connection': 'close',
    'Date': 'Tue, 21 May 2019 23:10:09 GMT',
    'Content-Type': 'application/json;charset=UTF-8'
}

response_text ={
    "timestamp": "2019-05-21T23:10:09.945+0000",
    "status": 500,
    "error": "Internal Server Error",
    "exception": "com.netflix.zuul.exception.ZuulException",
    "message": "Read timed out"
}
1 Like
4

We also see this error still quite regularly. @Mattlassian I have reported this to Atlassian before and the current workaround seems to be to retry the request. From what I can tell this usually works the second time.

We also see regular 500 errors without any additional context from the search API (/ex/jira/[cloud id]/rest/api/2/search). Response is a simple 500 Internal Server Error with no other context. Here are some headers that may help to debug this:

x-application-context: "Stargate:prod,prod-east:8080"      
x-failure-category: "DEPENDENCY"      
x-request-id: "eb6e45aac5660463"

@akassab any idea who at Atlassian could look into this? Happy to provide more details in a DM. Should I open a DevHelp issue instead?

4 Likes