JQL for Updated Date > Closed Date

[Rob B]

Users want to filter issues that have a 'greater' updated date to the closed/resolved date.

[Thomas Schlegel]

Hi Robert,

with plain Jira, this is not possible. If you have the Scriptrunner app, you can do the following:

issueFunction in dateCompare("", "updated > resolutionDate")

[Rob B]

Hi Thomas,

I need the 'Updated' date as follows....

[Thomas Schlegel]

you asked for the filter - with that filter you get a table of issues. Which columns you want to see is your decision then.

[Rob B]

It seems also to be pulling off issues that have the same 'Updated' as 'Resolved' date?

[Thomas Schlegel]

I think the datecompare function also compares the time portion of the datetime. Is this the cause in your example?

[Rob B]

Some have the exact same date and time to the minute, if those issue werent in the list it would be perfect.

[Thomas Schlegel]

@Nic Brough -Adaptavist- - is Scriptrunner comparing seconds also?

[Nic Brough -Adaptavist-]

I believe it compares the whole timestamp it gets from the database, so yes it would, although I didn't think Jira bothers to save seconds.

[Rob B]

Im trying to run this when we have 1.3 million issues and this is timing out i think, so im combining it with JQL with no luck.

Do you have any advice on helping the time out problem? Thanks

[Thomas Schlegel]

How did you combine it with JQL? Maybe it makes a difference if you add the additional JQL before or after the datacompare.

[Rob B]

created >= -10d AND issueFunction in dateCompare("", "updated > resolutionDate")

I just tried the created after it with no luck as well. I thought it being first would help :(

[Helle Overbeck]

Hi

I just had a similar experience - but when I put all the parameters into the datecompare, then it ran a lot faster (by me). Try this:

issueFunction in dateCompare("created >= -10d","updated > resolutionDate")