There are a number of places that we want the UI for project_issue to use color-coding based on the issue status:

We need a consistent, unified system for this. Basically, all of these places need to use the same CSS classes on the appropriate wrapper HTML elements, and the CSS should be written in such a way that we only define the colors for each class once.

Note: I'm explicitly *NOT* talking about #1721768: Allow site admins to associate colors for issue status values via the UI here. Once we ensure that all the color handling stuff is unified, we can contemplate making it possible to define those colors via the UI. For now, I'm happy to leave some default colors in project_issue.css and let sites override via their theme as needed. But, it's essential that we don't have 4 sets of colors for those 4 different places that we use status-based coloring in the UI, and it'd be nice if you only needed a single CSS selector to define each status color.

Comments

drumm’s picture

Priority: Normal » Minor

This isn't a Drupal.org D7 launch blocker. It is a welcome cleanup if a volunteer can take a look at it.

dww’s picture

My only concern is that we don't introduce inconsistencies in the UI due to this. But I agree, this isn't a launch blocker.

drumm’s picture

(We can tackle this before launch if we are working on this code anyway, but shouldn't go out of our way to fix it.)

drumm’s picture

Issue tags: -drupal.org D7 +Drupal.org 7.1
drumm’s picture

Issue summary: View changes

added link to #1721776

tvn’s picture

Issue summary: View changes
Issue tags: +drupal.org hitlist
tvn’s picture

Issue tags: -Drupal.org 7.1 +d.o issue workflow