@Jose Daniel Rodriguez I'm almost a year late, but I just ran into this myself and was able to get by it but adding another condition to my behaviour, an 'except' condition for just the 'Create' step. This appears to be working for us.
So in our case, we're restricting a field to 'Readonly' when it's in an 'On Hold' status, and like you, when we created a ticket, it was also restricted at that step. Addind another condition (except) to the same behaviour, for action 'Create' solved this for us. Creating tickets works as expected, the field is not restricted, and then when it goes into 'On Hold' is is restricted.
Conditions:
In the most recent version you can use the initialiser function. In all cases other than create there will be an issue already created, so you could use something like:
if (! getUnderlyingIssue()) {
getFieldById("duedate").setReadOnly(true)
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.