Change Task State

[Cirrus]

Need some help as to the best way forward please.

I have a requirement to prevent users from starting change tasks when the associated change request is not yet in implementation. The best logic I can think for this is to make the task state read only until the scheduled start date on the request = current date/time, because often a user will start work on the change but forget to change the state to Implemetation, so we cant use the change request state. We can live with that! I have tried creating a business rule to add the change schedule start date to a scratchpad, and then an on submit client script to compare current date to start date, and to set the state field to read only using g_form if current < start, but it doesn't work. Similar posts have suggested using ACLs, so should I be looking at a scripted condition here (there is already a write condition in the request state is not on hold, which suggests it might 'overrule' such a condition). Any suggestions appreciated. 

[Mark Stanger]

I'd go with the ACL here.  You're right that you'll have to make sure this works along with your existing ACLs though.  You'll need to create/modify an ACL for the 'change_task.state' field for the 'Write' operation.  I modified an out-of-box ACL as shown in the screenshot and that's working great in my instance.  The last line in the condition builder is what you'll need to make this work. (Change request planned start date is at or before last minute).  It's not up-to-the second, but it should be close enough and doesn't require any scripting.

[Mark Stanger]

Has this question been answered or is there more information I can help you with?  If it's been answered, please mark the answer above as the correct one so people know this has been taken care of.  Thanks!