2018-07-19: UI doesn't report about 502 errors when ToDo checkboxes are checked/unchecked in an Issue
If an Issue has many (say, 100) ToDo items (those which are created with
[x]in markdown), multiple UX problems might appear:
During the process of saving, user doesn't understand that the process of saving the checkboxes state is not finished – no "preloading" signals after she/he checked or unchecked a checkbox.\
If request to save the state (PATCH request on the screenshot below) is failed due to 60-second timeout, the user isn't notified about this failure and can continue to think that everything is fine and work is saved.
Noticed it many times during July 16-18, here is an example:
- User can check/uncheck the same checkbox multiple times. The final state of the checkbox saved in the DB might be not what the user expected.
In this example I checked and right after that unchecked the 2nd checkbox which was initially unchecked:
– I expected that after my single check and following single uncheck action the state of the 2nd checkbox will be "unchecked". It is not so, as we can see from the screenshot and what is can be also verified with reloading the page.
Related "backend" issue about bad performance and 502 errors of mentioned PATCH requests: https://gitlab.com/gitlab-com/production/issues/331