I created next-gen project, added some issues and logged hours to them
I tried to find the issues by using this jql:
worklogDate >= "2019-11-01" AND worklogDate < "2019-12-05"
but it did not return my issues with logged hours (list of results was empty)
Does it mean that worklogDate is not supported in next-gen projects?
I found this bug: https://jira.atlassian.com/browse/JRACLOUD-73492
If you are encountering problems searching for issues in JQL using the worklogDate, you can add the time tracking field to the issue type and the issues will then appear in JQL.
Adding time tracking field to issue type, does work, but this means that Time tracking field needs to be each issue type for each next gen project.
Is this how this going to be always going forward, or is this a bug which is currently being worked on? This used to work earlier without the workaround.
Is there any other way to query the worklogs which does not require this workaround?
Hello @Harsh Agarwal [AIO]
Thank you for your question.
Actually, the expected behavior is that you should not be able to log work on Next-gen projects if don't have the time tracking field added to it.
The logic behind that concept is that the ability to log work in issues only makes sense when you have an estimation to measure against it since it is an accurate metric, different from Story points.
That being said, the bug informed before was created to make the time tracking field required to customers that want to log work in the issues.
Let us know if you have any questions.