Move an artifact from one tracker to another means: 1. export the artifact to XML 2. delete the artifact 3. import the artifact export at step 1 When the platform is configured to have async jobs, delete is automagically done async so we have: 1. (sync) export the artifact to XML 2. (async) delete the artifact 3. (sync) import the artifact export at step 1 When things go wrong, the async is still being processed while step 3 started, that means that random data can be deleted in the newly created artifact, like the global rank. As move must be done "in real time" for the end user, the proposed solution is to force delete to be in synchronous mode, even on async platforms so all steps are performed in the logical sequence. How to test ------------ * Have Redis configured so Tuleap can perform async jobs * Move an artifact from one tracker to another => Global rank of this artifact must not be lost. Change-Id: I39459ab855414e19495436fbb858d9b838a8c142

+75 −26

Author

Yannis ROSSETTO (rossettoy) 2022-11-17 18:22

Committer

Yannis ROSSETTO (rossettoy) 2022-11-18 16:29

Hash 1e98a1ec0a2831dbc15e579986668ba84f3c711f

Parent f5233d54524becc2de0707b3e7d334ca9a8fa16d

Reference git #tuleap/stable/1e98a1ec0a2831dbc15e579986668ba84f3c711f