"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?

[Tetiana Bondar]

Hello @Tuncay Senturk _Snapbytes_ , @Trudy Claspill !

We're currently using the /rest/api/3/search/jql endpoint and filtering issues with:
worklogAuthor in ("accountId1", "accountId2") AND worklogDate >= "2025-07-01" AND worklogDate <= "2025-07-15"

It works for now, but we've noticed that worklogAuthor is no longer listed in the official JQL fields reference here:
https://support.atlassian.com/jira-software-cloud/docs/jql-fields/

This raised concerns on our end — especially since we're using it to filter worklogs by user. There is no deprecation notice (yet), but the fact that these fields are missing from the new docs may suggest they're undocumented/internal and could stop being supported in the future without much warning.

Would love to hear if others have official info or recent experience on this as well.

[Trudy Claspill]

I have not seen any information about the field being deprecated, but I do see, now that you mentioned it, that the field is not listed in the supported fields for JQL documentation.

I also did not find anything in the public Atlassian Backlog concerning the lack of support for the field.

I advise you to open a support case directly with Atlassian about this to find out if the field is in fact being deprecated or if this is some known bug. It would be great if you share back here anything you learn.

https://support.atlassian.com/contact/#/

[Tetiana Bondar]

@Trudy Claspill thank you for the answer and advice!
I created a ticket.
I will share the results.