-
Bug
-
Resolution: Won't Fix
-
Low (View bug fix roadmap)
-
None
-
5.0
-
None
-
5
-
Given all the trouble with these fields for the past year, I am not sure if this change was intensional or some code was not moved correctly to the 5.0 level (I haven't looked at 4.4.5 yet). Testing against 5.0 and found the tests broke between 5.0-rc1 and 5.0. Here is the conditioning I now have to have in my tests
cascadeSelectByValue = (info?.version > '4.4') && (info?.version < '5.0')
In other words, after 4.4 got values and after 5.0 it reverted back to pre 4.4 support (ids).
- is cloned from
-
JRASERVER-25732 Cascade select secondary value must be specified as an id
-
- Closed
-
- relates to
-
JRASERVER-25034 Multi-select custom field value handling incompatible with previous releases
-
- Closed
-
I understand and agree with the direction, however, there needs to be a difference between not making improvements and fixing obvious regression problems and introducing incompatibilities. This can cause major headaches for upgrades. For an interface that was suppose to be stabilized, there has been a lot of breakage in the 4.x/5.0 time period. Please ensure SOAP APIs retain upward compatibility and regressions get fixed.