Change to REST API worklog/updated nextPage URL?

[Kennedy Schnieders]

Caught this issue today due to a failing workflow - for reference this workflow has been running daily since June 2023 without this failure, so my assumption is that something just changed.

The REST API endpoint /rest/api/3/worklog/updated provides a nextPage URL for the next set of updated worklogs. As of writing this, both in the REST API documentation (link) & actual use, the nextPage URL returned on a successful request has the following format: rest/api/3/worklogupdated?since=...

I am not sure if this is a recent change, or if this is how the nextPage URL has always been, but if this nextPage URL is used as-is now, the result is a 404 error.

In order to fix this, we are replacing worklogupdated with worklog/updated in the above returned URL.

This is not expected behavior given the REST API documentation. Just wanted to make others aware.

[Nashid Farhad]

Hi @Kennedy Schnieders 

This change wasn't an intended change - I'm afraid. We've had a minor incident and the issue should now be resolved.

Here's the Statuspage entry of the incident.

https://developer.status.atlassian.com/incidents/yb75slflv2fv

Apologies for the inconvenience.

[Sunny Ape]

Thanks for the quick response @Nashid Farhad , much appreciated.

[Kennedy Schnieders]

Thanks, @Nashid Farhad ! Appreciate the quick turn-around on this.

[Sunny Ape]

The documentation for that endpoint does show in the example response that worklogupdated is the expected response for both the self and nextPage objects, not worklog/updated, so I'd recommend trusting the documentation on this occasion.

It's the same for some other GET endpoints such as worklog/deleted which returns worklogdeleted as the path in the response.

However, it is silly that the responses provide an invalid path that can't be resolved, so I'm inclined to think it's a bug in the responses and the forward slashes have been accidentally omitted from the path.

I'd suggest that you log it with Atlassian as a bug.