What does "updated" JQL actually cover? Edited

I am wondering what does the "updated" actually means in JQL: Does it cover absolutely any change to the issue or is just some particular modification?

For example, if a user logs time under the issue, does that mean that issue was "updated"?

2 answers

2 accepted

Accepted Answer
2 votes
Tarun Sapra Community Champion Aug 10, 2017

Hello Ina,

"Updated"  does cover any change to the issue. And Yes logging work/time on an issue is covered by the "updated"

Hi @Tarun Sapra

This is great, thank you.
Is there a way to specifically look for updates in the worklog/time?

For Example:
worklogDate >= "2017/08/01" && worklogDate <= "2017/08/11"

- Is this going to filter all updates on the worklog between those days?

CC- @Umer Saeed

"Is this going to filter all updates on the worklog between those days?"

No, that's not the case. Because workLogDate basically means the "Date selected" while logging work - https://jira.atlassian.com/browse/JRASERVER-1959 

This date can be in future as well. So the JQL which you have shared will only fetch issues which have the workLogDate in the specificed time-period.

For example - You can log your work on an issue today and while logging work select the workLogDate as 20 August. So when you search using "updated" field like 

updated > startOfDay() 

Then you will get the issue which you updated with work log but if you try

worklogDate <  endOfDay() 

 Then you won't get this issue because you updated the issue today but the worklog date you selected is for 20-August

Okay, got it. 
So WorkLogDate is not connected to the act of updating but to the content you write there. 
Good to know, @Tarun Sapra

So when it comes to updates, the only thing I can actually query using JQL is the overall update on the issue (using the "updated"). 
Do you thing there is any way to specify that we are looking into updates of a specific information, which in this case is whether the worklogs were updated?


Accepted Answer
1 vote

'updated' specifically works for the following actions:







And you can use the preset functions for the timing periods, such as:

updated < startOfDay()


It doesnt really work for =, !=, is, is not, in, not in

And yes, it will be to find any action on the ticket that was updated within the given function timing period

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

26,071 views 2 7
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you