UI affordances not obvious
Summary
In the Merge request pages of Gitlab, the things a user can do by clicking on things ('affordances') are not obvious. Examples:
- On https://gitlab.com/loopinsights/portal/merge_requests , it's not obvious that clicking on the bold part of a merge request's title will take you there.
- On https://gitlab.com/loopinsights/portal/merge_requests/75 , it's not obvious what to click on to see the changes in the merge request. That is to say, the 'Open in Web IDE' button is much more prominent than the greyed-out 'Commits' and 'Changes' labels next to the bold 'Discussion' tab.
- On the WebAPI, it's not obvious how to get back to the merge request.
- When viewing the files via the 'Changes' tab, you have to hit 'back' once for every file you've looked at, unless you use the navigation bar to get back to the merge request page. View 10 files? Then hit 'back' 10 times.
Steps to reproduce
Create a merge request with a commit and a change.
Example Project
https://gitlab.com/loopinsights/portal/
What is the current bug behavior?
User gets frustrated trying to find the differences in the merge request.
What is the expected correct behavior?
User are happily viewing the differences in the merge request.
Relevant logs and/or screenshots
https://www.interaction-design.org/literature/topics/affordances