We have below scenario,
For the Epic issue type, the user will fill in the Due Date and the Base Due Date will be a scripted field that will capture the first Due Date value entered and lock it. So, if the user modifies the Due Date later, the scripted field does not alter the first value.
Thank you !
This is very simple. But do not use a scripted field.
Create a standard date (or date time) custom-field for "base due date". Put it on the "view" screen for the issue, but not edit, create or any transition screens. That gives you a read-only field.
The script then becomes simple, it just needs to read the due date and poke it into the target field in a post-function on the create transition.
Hi @Nic Brough -Adaptavist- - Thank you for the reply. But, will be possible to copy and lock the first value and not alter this value even if the Due Date value is altered ?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's what I've just defined in my answer.
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.