Feature Requests & Ideas

For bug reports and questions, please use the in-app chat or support@mabl.com.

Multiuser edits save conflict warning for better collaboration

As a user, I want to have the ability to lock or checkout flows so that other user will not be able to overwrite the flow the I am updating.

 

I have several instances where the latest update in the flow  was overwritten by other users since they are the one who last updated their script which is using the flow that I am updating.

  • Mark Russel Cruz
  • Jan 2 2020
  • Shipped
  • Oct 20, 2020

    Admin response

    Instead of checking out and locking a flow, which is not great for multi-user collaboration, mabl allows anyone with edit permissions to start editing a test and will warn users about conflicting changes upon save. If you see a save conflict warning you can either proceed with your changes or decide to save your edits to a test branch first. Release notes

    Changes saved to a test branch can be merged later, once you've had a chance to review other what changes have been made to the test prior to your edits. In general, we consider working with branches to be a better collaboration mechanism than locking artifacts during editing, which comes with its own set of challenges such items remaining in a locked state.

  • Attach files
  • Mark Russel Cruz commented
    23 Jan 07:56pm

    @Anton - I have discussed this to Thomas few weeks ago. I think he already covered everything regarding our questions and how we would like it to be implemented. Anyway, thank you for checking. 

  • Admin
    Anton Hristov commented
    23 Jan 07:30pm

    We are working on a solution for this issue and will update this request when shipped. Let us know if you would like to give us feedback on the implementation design before we ship it.

     
Copyright © 2020 mabl Inc. All rights reserved.