PUT API lacks means to protect overwriting outdated version of entity
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
When changing e.g. an issue description via API, there currently is no way to prevent overwriting changes somebody else made. One can fetch the issue right before making the change to minimize the likelihood, but we'd rather see proper support for it in the API.
Apart from the API, we see the same problem probably caused by old browser tabs and regularly manage to overwrite changes others have made to issue descriptions.
One simple option would be to send a timestamp, like last_known_updated_at when making a change and have gitlab fail the request if last_known_updated_at != updated_at and leave it to the client to refetch and deal with the situation.