Viewing issue id and project name in a project issue board and a group issue board
Description
Show project reference and id per the following:
Location | Project issue board | Group issue board |
---|---|---|
Issue card | #1234 |
gitlab-ce#1234 |
Issue sidebar | #1234 |
gitlab-ce#1234 |
For group issue board sidebar:
Previous discussion
Reducing visual noise
- In complex (albeit powerful UI) places such as issue boards, we want to reduce visual noise, so that the user focuses on just what is most important.
Issue id
- When you are looking at an issue board, it is not that important to know the issue id.
- As a user, when you look at an issue card, you recognize the issue by the issue title, not the id.
- Teams typically refer to issues by name in verbal communications.
- In written communications, we copy and paste links typically, e.g. exchanging issue links in Slack.
- Inside GitLab, GitLab does it for you automatically, e.g. when we link related issues together, links are created.
- So there's no actual rigorous use case that requires you look at an issue id (which can get really long!), memorize it, and then write it down somewhere else.
- So the issue id itself is not that important when looking at an issue. In particular, when viewing an issue board, it's not that important to actually see the issue id of issues in the issue card itself.
Project name
- When viewing a group issue board, most users typically do not care that one issue is from one project versus another, at least at a high-level glance. (This is debatable! Since we haven't even released the feature!)
- Again, I recognize the issue from the title itself. And since I'm looking at a group board, I know that the issue belongs to the group, and I don't really care in which specific project. This is because I am looking at the group board view, and the use cases here are planning, moving issues around different lists. It is not lower-level project-specific issue management.
- Once I click into the issue, then I might care about which project it belongs to, because of project-concerns, such as which repo it belongs to.
Edited by Victor Wu