Worklogs not being saved

[Matthew FitzPatrick]

When adding a new worklog since March 22nd, The REST api comes back with a 201 response and the JSON returned seems to be correct, but nothing is displayed in worklogs or reports. This is affecting all of our users in the same way.

It's not clear of newly entered timelogs fails to save or fail to display. Is anyone else seeing this in their accounts?

[jeffrey_lee]

seeing this as well:

it always says "Worklogs are empty", regardless of what was entered with "+ Add Timelog"

[YY Brother]

Hi @Matthew FitzPatrick 

Welcome to our Community. May I have some backgrouds firstly?

• What's your scenario? It seems you're using REST API to add worklog for certarin reason;
• What API are you using? Please provide the input parameters, the endpoints and some necessary screenshots. 201 code should be successfully added.

Thanks,

YY哥

[Matthew FitzPatrick]

We are using the cloud hosted web interface as shown below. This web interface makes a REST api POST with a 201 response, but the logged time doesn't show anywhere in the UI for anyone even after refreshing.




POST: `https://XXXXXX.atlassian.net/rest/api/3/issue/1234567/worklog?_r=1711387989159`

[YY Brother]

have you tried postman to do post arequest of this API call with the same request parameters and body? what's the reault then?