Automation trigger on release start date

[Fong Xu]

Hi,

I am creating an automation rule in Jira automation section. but i am not sure how to create a trigger on Release dates, such as start date. I know that when you enter a fix version on a jira card, the release date is defined by default. So I think I can use the release start date to trigger an rule. Any suggestions? 

Thanks,

Fong

[Nic Brough -Adaptavist- · Accepted solution]

I think your second script is closest to what you need, but it's worth explaining what Jira is doing.  When you look at this field on an issue, there are three possible types of response:

A list of values that includes TBC (return false)

A list of values that does not include TBC (return true)

Nothing, because there are no values selected, although Jira displays "none" in lists or hides the field completely (I think you want to return true here too)

So, I might be a lazy coder and write:

if ( cfValues['Testing required Up/Downstream']*.value )

{

   if ( cfValues['Testing required Up/Downstream']*.value.contains("TBC")

   { return false; }

}

return true;

(That says "if there is a list of values, and one of them is TBC, false, but for other cases, where there is a list without it, or no list at all, return true)

[AdamCliff]

Hello,

That was throwing the same error as my script. None was being seen as an error.

Finally got it to work though using the following line

!('TBC' in cfValues['Testing required Up/Downstream']*.value)

Thanks all for your help

Adam

[Joe Pitt]

I believe None is actually null in the database like Unresolved