HI Team,
I am looking to configure a job using Adaptavist scriptrunner plugin to check if any changes have been made to a column of a table within last few minutes?
Is the second scripted field on the same issue as the first one?
This will often break because you can't be sure which field will be recalculated first when the issue is reindexed (or, in fact, how many times!). The way to "fix" that is to not base a scripted field on another one if they're going to be indexed in the same batch (i.e. same issue). Most of the time, you have to duplicate the code.
If, for example, you have
field a = x + y
field b = a + z
Replace the second one with a duplicate calculation, such that field b = x + y + z
Thanks for your answer! The scripted fields are for different issues.
The first issue is of type A and has a scripted field AFunctionalProgress. The second scripted field (the new one) is for issue type B and therefore its name is BFunctional Progress. Multiple issues of type A could be linked to type B. I iterate through all these issues of type A and try to get AFunctionalProgress with the mentioned code.
It is strange that the thing you describe always works in our cases. For issue type A, we have the scripted fields AValue1 and AValue2 where AValue2 needs is based on AValue1.
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.