Posted by D34dMan on May 29, 2016 at 6:14pm
Red ( default )
4% (1 vote)
Blue
8% (2 votes)
Green
65% (17 votes)
Yellow
4% (1 vote)
Grey
19% (5 votes)
Total votes: 26
What colour do you prefer for "Closed (fixed)" issues in https://www.drupal.org/project/issues/XXXX page?
Group categories
Group Tags
- Community Tools Team (2)
- Developer Tools Team (13)
- week notes (29)
Hot content this week
-
7 years 9 weeks ago
-
15 years 39 weeks ago
-
16 years 41 weeks ago
-
6 years 11 weeks ago
Comments
Reason why i created this poll
Red colour is something which is to be used to grab attention. Right now if we visit this link https://www.drupal.org/project/issues/drupal?status=7 it is red mania over there. None of those issues actually needs any attention. In my opinion they should be greyed out. But i would like to hear other's opinion too.
I am personally using a custom css for Drupal.org which does the modification. So if there is a favourable response in here we can try to create a patch.
Here is my code,
.project-issue .state-7 td {background: #fefefe;
border-top-color: #eeeeee;
}
Green
Thanks for bringing this up!
The current palette is IMHO opinion ugly, illogical and a overall very bad choice (so almost any change would be to the better).
However, the current palette has clearly been designed, and while I of course cannot know what its original designer had in mind, it looks to me like the idea behind is to communicate issue progression to the user (not the maintainer) in a way that is supposed to make sense to the user.
So I think the progression of a "normal" issue is designed to look like this to the user/reporter:
Active - grey (just created, waiting for action)
Needs review - yellow (fixed? waiting for evaluation)
Needs work - light red (nope! - we can't use this, cul de sac)
RTBC - light green (yup! go ahead and commit)
PTBP - light green (yup! go ahead and commit)
Fixed - green (fix committed - all set to proceed to the final stage)
Closed (fixed) - red (this issue is now officially closed. Do not reopen!)
"Closed (cannot reproduce)" is also red, presumably to tell the user that the issue is considered fixed, and is not going to be worked on.
The state "Closed (outdated) is grey (#f9f9f9), the same as "Active". I must admit that that does not agree with my theory about this in attempt to communicate progression to the user. I think is should have been red like the two other closed states I have mentioned.
Then there are the three blue "Closed" states, along with the two blue "Postponed" states. I can't make sense of this either, but maybe the original designer of the palette just deemed that these doesn't fit into the issue progression colour scheme, so let them have a different colour?
I agree that the issue state palette should be changed, but I don't think it is a good idea to just change the colour of one state, as it would just make the whole palette even more illogical than it already is.
If we're going to change this (and I think we should), then the whole palette should be reworked by an UX expert, and complete alternative palette should be proposed here for the community to vote on.
Closed (outdated) had wrong CSS in groups.drupal.org
Closed (outdated) had wrong CSS in groups.drupal.org. On D.O. i has shares the same style as that of Closed (Works as design). So i have edited the table row class to give more visually correct idea. Sorry i failed to observe that earlier.
thanks for chipping in, your valuable comments did give me another perspective into the colours.
How do we get this change made?
The red really annoys me, and clearly a few other people. How do we get this change made?
Do we need to engage a UX expert? Can't we get this initial change done while that is organised?