Cloud ScriptRunner Date Custom Field Validator

[Zita Bagi]

I have a question about validating date customfield in Cloud.
this:
new Date(issue.customfield_10061).toISOString() > new Date().toISOString()
Still gives an error:
Evaluation failed: "new Date(issue.customfield_10061)" - The date has invalid format. Expected: ISO-8601, for example: 2011-12-03T10:15:30

I tried different versions:
//new Date(issue.customfield_10061).toCalendarDate("yyyy-MM-dd") > new Date().toCalendarDate("yyyy-MM-dd")
//(new Date(issue.customfield_10061).format("yyyy-MM-dd'T'HH:mm:ssZ")) > new Date().format("yyyy-MM-dd'T'HH:mm:ssZ")
//new Date(issue.customfield_10061).format("yyyy-MM-dd'T'HH:mm:ssZ", TimeZone.getTimeZone("UTC") > new Date().format("yyyy-MM-dd'T'HH:mm:ssZ", TimeZone.getTimeZone("UTC")

But I keep getting this same error message.
Can you please let me know how to parse a date custom field so taht it would be ISO-8601, if not with .toISOString()?

Thank you!

[Christian Czaia _Decadis AG_]

How are your versions ordered? Maybe you could use fixVersion < XXX and fixVersion > YYY

[Ramiro P]

I think it is the same case as here:

https://jira.atlassian.com/browse/JRA-25901

This won't be easy but the only workaround I found is the one explained there, but you have to update the filter everytime a new version is created.

[richie_gee]

Hi there,

I think you can achieve by a little help on advance searching:

project = TEST AND fixVersion = EMPTY AND updated >= 2013-01-01 AND updated <= 2013-03-31

Replace the project name, and the updated date presuming your quater is 1st Jan to 31 March.

Cheers :)