Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #42972 Better concurrency handling
    Actions
    Infos
    #42972
    Tuleap PCC (tuleappcc)
    2025-05-09 14:26
    2025-05-07 17:29
    44654
    Details
    Better concurrency handling

    As a: Tuleap user
    I want: to encounter less concurrency conflicts
    So that: I can effectively collaborate on artifacts with others

    We have many users who are all collaborating on a single artifact in Tuleap. For instance, one person may be updating the status while another user is making a comment, and another user is changing the text in the description or title. While none of them are changing the same data as the other, they all still get concurrency issues and end up overwriting another's work.

    We would much prefer that concurrency checking happen at the field level rather than the artifact level so that we can better collaborate on a single artifact. Upon Save, edits to fields should be saved, but fields that were not touched should not update the value in the database (regardless of what the user saw locally on their screen).

    Empty
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Tuleap PCC (tuleappcc)
    Stage
    Empty
    New
    Empty
    Attachments
    Artifact links
    Empty
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Tuleap PCC (tuleappcc)2025-05-09 14:26

    We like the concurrency warnings that are currently presented - but they don't allow for the user to say "yes, please keep those changes" - only to acknowledge each one and then have them be overwritten by their own changes. That could be another solution here, just allowing users to select which concurrency conflicts they want to keep what the previous user did vs. overwrite with their change.

    This is a daily occurence, I would say. We have instructed our users to save often and refresh the page just prior to making any changes, and it still happens, especially as we use Tuleap to track bugs incoming from our clients. We are all very eager to hop on and provide help by modifying the bug, and often run into concurrency issues because of that.

    Let us know if we can provide any additional information here! Thank you!

    User avatar
    Manuel Vacelet (vaceletm)2025-05-09 10:03

    Note that we should anyhow inform users about concurrent edition but conflict could be resolved at field level indeed. Do you have an estimation on how often it happens on your platform ?