Impact of setting custom field value from scripted field

[Vedant Kulkarni]

Is anybody aware of the impact of setting custom field value from the scripted field? Please help me to understand it.

I needed to fetch the scripted field data from DB. I copied the scripted field value in another custom field so that I can fetch the duplicated custom field from DB, but not sure what would be the impact of this.

[Benz Kek _Adaptavist_]

Hello Vedant,

From what you described, it shouldn't cause much issue if you are copying the Scripted Field value from another custom field. 

Perhaps you can share more on the Scripted Field configuration (like its type and script) and the custom field you are copying it from (using what ScriptRunner features to copy, the custom field type, and script) then we can look further into it. 

Regards, 

[Vedant Kulkarni]

Thanks for the response @Benz Kek _Adaptavist_.

 The scripted field is a result of some calculations performed using groovy code and returning the value in number format. As you know we cannot fetch this scripted field data from the DB, so I'm trying to set another custom field value from a scripted field code. So that the duplicated custom field can be fetched from the DB.

But not sure about the impact of this, have you come across such cases?

[John Funk]

Hi Vedant - what does the value look like? And what type of custom field is it?

Just because it came in from a scripted field, I don't see anything that would cause an issue. 

[Vedant Kulkarni]

Thanks for the response @John Funk .

The scripted field is a result of some calculations performed using groovy code and returning the value in number format. 

[John Funk]

I think you should be good then.