Show nothing instead of unassigned on issues #8155
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've prepared a stage. Click to open. |
cirosantilli
changed the title
|
👍 I think this is a good idea. It de-clutters the UI. |
dblessing
changed the title
dzaporozhets
added a commit
that referenced
this pull request
Oct 27, 2014
Show nothing instead of unassigned on issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Subjective like all UI features, but here goes:
After:
Before (shows
unassigned):I think it's natural to understand that if there is no "Assigned to" then there it is unassigned.
Otherwise it produces too much interface clutter, e.g. from GitLab CE:
When we have a single object to show, saying
not thereis OK. But on lists / tables where information is already overflowing, I'd rather not show anything.