Using task release for resolving parallel conflicts at the time of checking in objects

After the work in Synergy is completely task-based, the object release only has informational character about the release to which the object was checked out.
Nevertheless, when checking in an object, the object release is used to check whether a parallel version is to be resolved. This can lead to errors during task-based work, which I have described in more detail below.
The function "Show Parallels" is also based on the object release and is therefore also faulty.
The function "Detect Membership Conflicts", on the other hand, is able to detect correct parallel versions and display them under conflict as "Parallel Changes".

Please fix the problem by using the task release like in the detection algorithm of the Detect Membership Conflict for checking for parallel versions, if a object should be checked in. Please fix the same for “Show Parallels”.

Description of errors
First error: Unnecessary merge
In the attached picture "History_of_Mohn.jpg" you can see that the objects “Mohn.txt-3” and “Mohn.txt-2.1.1” have the same object release "Spielwiese/2.0". However, the task release of the task of object “Mohn.txt-2.1.1” has been changed to the release "Spielwiese/3.0". “Mohn.txt-3 “is in the state “checkpoint” and can not be changed anymore.
If you want to complete the task “skm_ueb#1479”, you get the message: "The complete operation stopped because parallel versions were found". Now you are forced to resolve a(n actually non-existent) parallel conflict.
Regarding task based work there is no parallel conflict: If your project is associated with release “Spielwiese/2.0” there is only one candidate: Mohn.txt-3. And if your project is associated with release “Spielwiese/3.0” the one and only candidate is “Mohn.txt-2.1.1”.

Second Error: Skipped merge
In the attached picture "History_of_Veilchen.jpg" you can see that the objects “Veilchen.txt-3” and “Veilchen.txt-2.1.1” are in danger of becoming parallel versions. The task release is equal, but the object release is different. The task skm_ueb#1489 is ready to complete. Unfortunately the completion of this task will work without stopping like described above. After completion of the task the two versions of “Veilchen.txt” are parallel versions that need to be merged. If your project is associated with release “Spielwiese/2.0” there are two candidates. If you use an “update” it is arbitrary which version you will get and which version you will miss.

This RfE is created according to case TS001516472.