Disabled Checkboxes Should Have Hover Text Indicating Why You Can't Check Them

Problem to solve

It is not simple enough to determine why checkboxes in Gitlab are denied being check. The system could do much more to communicate the rules that are resulting in disablement.

Further details

Use Case 1: Someone closes a MR afer opening it and I visit it via my email - at first glance it looks like I should be able to check the boxes like ones that aren't closed before I get to them.

Use Case 2: This is now a use case of the struggle not having this simple information creates (still not solve)

Since we upgraded from 10.0.1 to 10.4.7, when markdown checkboxes are added to a merge request, people who only have "Developer" to the repo cannot check the box interactively with a mouse click. Instead, they get a red X when hovering.

It does not matter whether the comment was created by a 'Master' or a 'Developer' - only those in "Masters" can check the boxes.

Screenshot of a developer trying to click the checkbox is attached.

We are fairly certain this worked before 10.4.7.

Can someone comment on whether this is a known issue (actually changed behavior) and whether there is a setting to revert the behavior?

FYI - we went to 10.4.7 - and not the latest - because we are trying to catchup on releases over time - so we don't provoke any problems or user confusion by taking too many increments at once.

Proposal

Have the hover text of disabled checkboxes indicate a one-line summary of why they are uncheckable.

What does success look like, and how can we measure that?

Hover text of disabled checkboxes indicates a one line summary of why they are uncheckable.

Links / references

/cc @jkrooswyk @aolson