•  
      request #29616 Move artifact must process synchronous deletion
    Infos
    #29616
    Yannis ROSSETTO (rossettoy)
    2022-11-21 10:51
    2022-11-17 18:21
    31208
    Details
    Move artifact must process synchronous deletion

    Given an artifact you want to move to another tracker, and given your Tuleap instance is configured to perform asynchronous actions (Redis is configured), then the move action will finish the deletion action after recreating the artifact in the new trackers, which means lose of data like the global rank.

    In the move action, even if asynchronous actions is configured, the deletion must be done synchronously to avoid data lose.

    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.

    Trackers
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Yannis ROSSETTO (rossettoy)
    Closed
    2022-11-21
    Attachments
    Empty
    References

    Follow-ups

    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    • Summary
      -Move artifact must process synchrone deletion  
      +Move artifact must process synchronous deletion  
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes