Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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.

1 answer

1 accepted

0 votes
Answer accepted

Hello @Piotr Bogacz

Thank you for reaching out.

Just to clarify, has the workaround provided in the bug worked for you? 

If you are still facing this problem, please let us know so we can further investigate it.

Hi,

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 @AIO Help

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.

We have the same issue, I think the field worklogDate is not been filled in the rigth way when the issues were moved to a new project.

Please you help.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,188 views 10 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you