Is it possible to find issues by using jql with 'worklogDate' in next-gen project?

[Piotr Bogacz]

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.

[Philippe Aubin · Accepted solution]

Hi Sergey, 

You can always create an OU and setup your base directory with that OU.

i.e: in your AD user create a JIRA OU and point that path in the Base DN when you setup your LDAP.

image2015-6-18 9:13:25.png

[Sergey Kiselev]

Thanks

[Philippe Aubin]

Always a pleasure ;)

[Nic Brough -Adaptavist-]

Possibly.  The licence is counted against who can log it.  That is determined by the groups named as users and/or admins in global permissions.

If you take 1000 users, and put 200 of them in a group called "JIRA users", then you will consume 200 licences if you use that group in JIRA to say "can log in".  The other 800 won't count.  (But they can't log in either)