"worklogAuthor" field in JQL is no longer supported in Jira Cloud REST API v3

[Tetiana Bondar]

Hi Community!

Our plugin development team encountered a critical performance issue because the worklogAuthor field in JQL is no longer supported in Jira Cloud REST API v3.

The essence of the problem: in our plugin we need to get only those tasks where the selected users left worklogs in a given period (for example, 2024-06-01 to 2024-06-30).
But worklogAuthor is now deprecated and this query does not work in Jira Cloud API v3.

Because of this restriction our team are forced to get all tasks from projects that the user has access to.
Then download all worklogs for each task....
And only after this step filter by author.accountId - after data creation.

There are difficulties because: 
1. Huge API load
2. Slow processing
3. Inability to work efficiently with large projects or date elements


I think not only our development team that has encountered problems due to the "worklogAuthor" is now deprecated in Jira Cloud REST API v3.
Maybe someone has found a solution to this problem?

I would be grateful for any information that could help in this case!

Product owner,
Tetiana 

[Trudy Claspill]

Hello @Tetiana Bondar 

Welcome to the Atlassian community.

I don't have an answer for you but I was hoping you could provide more information about your scenario.

1. Which endpoint are you using?

2. Can you provide an example of the call/payload you used that work in v2 that no longer works in v3?

3. Did you see a deprecation notice that worklogAuthor is not supported in v3, or did you discover it when you api call stopped working?

4. What is the response you get in v3 when you try the api call?

[Tuncay Senturk _Snapbytes_]

Hi @Tetiana Bondar 

Building on what @Trudy Claspill says, I've checked the Atlassian changelogs and couldn't find any deprecation notice related to this. Could you please clarify why you think it has been deprecated?