Please note that while this issue has been resolved in 5.6.0 the status will let you know whether it has been Fixed, Answered, Obsolete or Won't Fix.

Obsoleted by GHS-1261

Hi Nicholas,

The projects that we have that actually practice Scrum properly tend to have quite small teams and thus theoretically card colour could be used to represent assignee. However, we tend to use different coloured sticky notes to highlight issues with certain properties, not the assignee. E.g. important issues, or blocked issues.

Thanks,

Ximon

Hello,

There are a few different ideas swirling around here now:

• by status/assignee/priority, or custom field
• icons, dots or card colours

Current questions that come to mind:

• Ximon, how many assignees do you have? Would colours really be sufficient to distinguish assignees?
• Matthew, you are talking about extending the highlight perhaps?
• Alan, Kathy, Pim, you talk of custom fields. Out of interest, what data do those fields hold?

It would be great if a few mockups could be provided, I believe that might spur the discussion further.

Thank you all, we greatly appreciate your input and feedback. Have a super week.

Regards,
Nicholas Muldoon

+61 2 8916 9125 (Australia)
+1 415 408 6147 (US)

Register now for Atlassian Summit 2010, June 9-11 http://summit.atlassian.com

So far, this idea is primarily about customizing the color of the entire card in GreenHopper. I have a slightly different slant on this idea - which is related to Andy Sanders' concern - drag/dropping cards into columns is great, but there's a limited number of columns that can realistically be displayed at once. I suggest a colored ICON that provides a sub-status, such as "swarmed" or "test cases drafted" or "tests failed" or "blocked" or the like. The icon should be displayed almost exactly like the red icon to the left of the "Blocker" status in the Priority field. But I would like this for a custom field. Presently, I call my custom field "Dot Color" because it simulates the physical dot colors that we have on our cards on our physical project whiteboard. Thus, the original color of the card can stay as is, and the color of a custom field's icon provides DETAILED sub-status info.

It would really be a tremendous improvement if it were possible to define your own field/value to color mapping.

With the current colors (Bugs in red, Sub Tasks in green) it's just not very intuitive and can actually be very confusing when you're just working on the issues. My first response to red is still 'NEEDS attention right NOW!' and to green 'oh, so that's OK already, phew!'... while most of the time it's should actually be the opposite!

I too would like to be able to have colour based on status.

The taskboard can only really support 3 or 4 columns yet even the default Jira configuration has more states than this.

However, the really value for this would be on the Planning Board where you can't currently see what's going on without reading lots of small text. The version summary on the right might give an overview, but you can't quickly see which tickets are in which state. Colours would make all the different ticket states leap out at you.

We are currently evaluating greenhopper for a client to replace a wiki-based solution. In this solution all cards are colored by the progress of the issue or at least by the status. To me it seems to be the last hurdle to take to go for greenpepper. Hence, I voted for this feature.

We need to color based on a custom field also.

We all want to use colors to highlight something different. We actually have a custom field which is important to us and which we would like to have colors mapped to. So why don't we just agree on a flexible concept that would allow the color coding to be based on any (user configurable) field?