`self` url return into search url instead of ticket url

Jira Development Jira Cloud
,
1

Hello!
This issue started on Tuesday (30/01/2024), we usually hit the api like this:

auth = HTTPBasicAuth(email, api_token)
headers = {"Accept": "application/json"}
query = {
    "jql": jql,
    "startAt": start_at,
    "maxResults": max_results,
    "expand": "changelog",
    "fields": "summary"
}
search_id_url = base_url + "/search"
search_id_response = requests.request(
    "GET", search_id_url, headers=headers, params=query, auth=auth
)

and it will returned like this

[
   {
      "expand":"<snip>",
      "id":"618430",
      "self":"https://api.atlassian.net/rest/api/2/issue/618430",
      "key":"<snip>",
      "changelog":{
         "startAt":0,
         "maxResults":5,
         "total":5,
         "histories":[
            {
               ...
            }
         ]
      },
      "fields":{
         "summary":"<snip>"
      }
   }
]

but suddenly when we hit the api again it returned a different result like this

[
   {
      "expand":"<snip>",
      "id":"618753",
      "self":"https://api.atlassian.net/rest/api/2/search",
      "key":"<snip>",
      "changelog":{
         "startAt":0,
         "maxResults":2,
         "total":2,
         "histories":[
            {
               ...
            }
         ]
      },
      "fields":{
         "summary":"<snip>"
      }
   }
]

As you can see above result, the self value has changed into the second result and it applied on every result that we hit.
Is there any changes on jira side or is this a bug?

Please kindly let me know if there’s anything. Thanks in advance!

Best regards

2

Hello @ClaudiaAnitaMagdalen

There seem to be a couple of problems with the self object being returned from various API endpoints suddenly changing. I’m currently discussing a near identical problem with someone in this Community forum thread.

I think someone at Atlassian might need to look into it further.

In the interim, I think you should lodge an official Bug report, as it is a fault.

1 Like
3

@ClaudiaAnitaMagdalen I confirm @sunnyape’s answer, adding a hyperlink to developer support.

1 Like
4

Thanks @sunnyape @ibuchanan ! I’ll report it as a bug.

1 Like