JQL query with worklogdate not returning results from one project

Question

I have a query running for an automation to update all issues which have time logged, but  an important custom field empty:

"Cost Category[Dropdown]" is EMPTY and worklogDate > startOfMonth()

The problem is, when I exceute the query, I get results for all projects except one, so the rule never gets executed for this project. Cannot figure out why this one would be skipped, while all others do fine. Does anyone have an idea?

Trudy P Claspill · Answer

I wonder if there might be some discrepancy between how date/time is recorded for a worklogdate and how startOfXXXX() is resolved.

Do the work logs in the "missing" project issues have date/timestamps that are greater than the first day of the month, regardless of whether they are recorded in your local timezone or in UTC?

I'm in the Los Angeles/America time zone. I just recorded time against an issue using the native Jira Log Work function. It is 11:30 PM on 5 November in my timezone.

When I execute a query like:

worklogdate > startOfDay()

...no results are returned. But the issue against which I just logged time should logically be returned.

I realize you are using startOfMonth() in your filter, so your query is a bit wider ranged than mine.

I recall when I worked with Tempo Time Tracking in Jira Data Center that the method it recorded time in the database table specify to Tempo was different than how the time was Jira's native database table for recording time.

Do you record work logs for all the projects using Tempo, vs. the native Jira Log Work feature?

You might consider using the Jira API to extract the worklogs for specific issues that are missing that you think should be included, and examine the work log data that is output to see if there are discrepancies.

Otherwise I recommend that you contact support for the vendor of the Tempo app and/or Atlassian Support. They would be able to examine the data in their databases directly to see if they can find an explanation. If you go that route, it would be great if you report back here what you learn.

Jasmina.Muhic · Answer

Thanks.

Issue security cannot be the cause.

Number of results is less than 100 without the missing project and shouldn't be higher than 200 with those issues included.

All projects are company managed software projects.

Yes, we use tempo to log time and the cost category field is a custom field on each issue type, used for grouping all the worklogs. The custom field should not be the root cause as I can query it correctly without the worklogdate parameter.

So, the worklogdate causes this project to be excluded in queries, but I cannot figure out why.

Trudy P Claspill · Answer

Issue Security settings can impact the display of issues in search results. If the user running the filter does not have permission to see the specific issue based on Issue Security, then the issue will not be included in the results.

There is also a limit to the number of results and a filter can return when it is executed through the UI, and when it is executed through an Automation Rule. Through the UI (i.e. the View All Issues screen) no more than 1000 issues may be returned. Through an Automation rule, it depends on the type of step in which the JQL is being run. Refer to https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

What is the project type of the project for which you get no results? Get that information from the Type column on the View All Projects page under the Projects menu.

Are you using Tempo to log time and using the Cost Category in each worklog? Or is Cost Category a field that applies to the issue overall?