Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

/rest/api/latest broken after update to 8.8.0

Michael Korn
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 9, 2020

After the upgrade from 8.7.1 to 8.8.0 I first realized that the assignee field in our Jira is broken, because tipping produces errors.

In the access_log I discovered that apparently all calls to rest/api/latest/... produce a 404 response, for example:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><status><status-code>404</status-code><message>null for uri: https://XXXXX/rest/api/latest/user/assignable/search?projectKeys=XXX&amp;issueKey=XXX-1024</message></status>

But if I replace "latest" by "2" is is fine!
If I try without authentication I also get 404, although it should be 401 (again: with "2" it is fine and I get 401).

Can someone explain where can I find the symbolic link from "latest" to "2" and how to repair it?

1 answer

0 votes
Michael Korn
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 10, 2020

Although that's not the exact answer to my question, my problems have resolved today: I updated the PlugIn "Automation Lite for Jira" to the newest version and the Issue ist gone. Unfortunately I have no idea what the connections are and how I can debug such errors in the future (the Jira logs didn't help at all).

Suggest an answer

Log in or Sign up to answer