You can't - the data for a scripted field only exists after the issue has been indexed, when it is too late to write new values to the issue. So you get a null because there's nothing there yet.
You need to forget the scripted field, and calculate what would go into it in your post-function to set the actual value.
Hi Nic/ Gabrielle,
Thanks for the quick reply. I need to copy the value of the Scripted field on to the Summary.There is some value written in the Summary. So I need to overwrite it with the Scripted field value( Which depends on the data entered in the create screen). As soon as create screen is pressed I need the value in the scripted field to appear on the summary
Instead of copying the scripted, why not just add a post-function called "Update parameters of the Set Field Value to constant or Groovy expression Function for this transition."
"The value of field <custom_field> of the current issue will be set to the result of a Groovy expression (unless the field already has a value)."
This way, the value will not be duplicated.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs