What does "updated" JQL actually cover?

[Ina Ivaylova]

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"?

[Tarun Sapra · Accepted solution]

Hello Ina,

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

[Ina Ivaylova]

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

[Tarun Sapra]

"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

[Ina Ivaylova]

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?

Cheers

[Umer Saeed · Accepted solution]

'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

[Georgia Harty]

Hello, 

Does 'updated' include when an issue is linked to another? I have the same issues showing in a JQL for both actioned and not actioned in the same time period. 

Thanks

[Harry Bob]

Can you confirm if you're able to use 'updated' like below?

updated >= 5m 

I tried it but doesnt seem to work. Cant seem to find any documentation regarding it.

[Hinnerk Mahnken]

Use -5m since its relative to "now" i guess

[Tommy Craft]

Does this actually work for anyone?

If I use

Status = "Waiting for Customer" AND Updated > -10m AND Organizations = "zzTest - Testing Org" 

in the Scheduled Automation JQL, it comes back as valid; however running it in the Issue Search returns no results.

If I use

Status = "Waiting for Customer" AND Updated < -10m AND Organizations = "zzTest - Testing Org"

then I get accurate results in the Issues Search but it fails validation in the Scheduled Automation JQL