Hi Jose,
The ticket you linked to is specific to the (in progress) 7.0 REST API, which is a completely different REST API than the 5.x or 6.x one. So, even if DS-4125 is resolved, it won't fix anything in 5.x or 6.x, as it's impossible to backport REST API changes
from pre-7.0 to older versions (quite literally the REST API is completely redesigned and rewritten).
So, long story short, if you are seeing a similar behavior in 5.x or 6.x, please log a different bug ticket, as it will need to be resolved differently. Do keep in mind though that this older REST API is deprecated as of 7.0 (So, in 7.0 it'll still exist alongside
the new v7 REST API, but that older REST API will be completely removed in 8.0). Because it is deprecated, it won't receive any new features going forward, and may or may not receive bug fixes (depending on the severity of the bug & whether we can find a volunteer
to resolve the bug).
I hope that makes sense
Tim