Configuration problem when one behaviour has two fields with the same name (scriptrunner 3.0.9 or superior)
*This issue has moved*
This issue has been moved permanently to Adaptavist's Product Support JIRA instance.
All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.
We have the "Component/s" field two times in one behaviour:
-The first time the component field is configured, it's Required in the step "En curso"
-The second time the component field is configured, it's Readonly in the step "Entregado",
If we want to add the component field is readonly at a new step (for example "En Planificacion") , we put the new step "En Planficacion" at the second configuration (components--> Readoly) But behaviour always add it to the first configuration (components--> Required)
It doesn't work since scriptrunner 3.0.9, but works correctly in scriptrunner 3.0.7
We suspect it´s related to incorrect $kount varible value provided by AddCondition class.
Please, could you provide us a fix or the source code instead?
I would just write it in code using a server-side validator. Depending on the current status or transition name, make the field either optional or required or whatever.
I am more likely to move the UI aspect to this and attempt to fix to be honest. Using code is much more flexible and powerful.
Do you have ETA for a fix? Need a bug fixed version or workaround. This is a critical bug.
Do you have any update about this issue?
Hi Miguel Angel,
I've been able to reproduce the issue in one of our instances and it definitely looks like whatever change you perform in the second field will go to the one above.
We'll investigate this further and we'll come back to you with more info.
We have tested the last version of Scriptrunner (3.1.4) and the problem persists.