Index![]()
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
Card colours allow you to quickly identify cards on your board as being of a particular issue type, priority, assignee, or — thanks to the power of JQL — practically anything you choose.
You can choose to set up your card colours in any of the following ways:
| Base your card colours on... | Explanation |
|---|---|
| Issue Types | One colour per issue type. A default colour will be allocated to every issue type which matches issues on the board. Default issue types and colours: Improvement, Task, New Feature, Bug. |
| Priorities | One colour per priority. The default colours are the same as used for priorities in JIRA. |
| Assignees | One colour per assignee. A default colour will be allocated to every user who is or has been an assignee of issues on this board. |
| Queries | One colour per JQL query. You can specify whatever queries you wish. Issues which do not match any of your JQL queries will be shown in grey. |
You can change the colours if you wish. You can also delete colours (for example, if someone leaves your team, you may want to delete the colour allocated to them).
Note that only the owner of a board (or a person with the 'JIRA Administrators' global permission) can configure a board's card colours.
In the 'Base card colours on' drop-down, select which method you want to use — either Issue Types, Priorities, Assignees or Queries, as described above.
For each Issue Type (or Priority, or Assignee, or Query), click the current colour to display a colour palette where you can select a new colour or RGB value.
Note that if you change to a different method of card colouring, your original settings will be retained so you can switch back to them later if you wish.
Screenshot 1: the 'Configuration' screen — 'Card Colours' tab.
Click the Card Colours tab.
For each Issue Type (or Priority, or Assignee, or Query), click the current colour to display a colour palette where you can select a new colour or RGB value.
Click the Card Colours tab.
Click the Delete button for the colour that you wish to delete. For Query-based colours, deleting a colour will also delete the Query.
Note that deleting a colour for an Issue Type (or Priority, or Assignee) will not delete that Issue Type (or Priority, or Assignee) from your JIRA system.
If you delete a colour for an Issue Type (or Priority, or Assignee) which still matches issues on your board, then that Issue Type (or Priority, or Assignee) will be automatically reinstated on the Card Colours configuration tab when you refresh the screen, and a default colour will be applied.
Click the Card Colours tab.
Hover over the vertical 'grid' icon, then drag and drop the colour up or down to its new position.
For Query-based colours, the order is important as each issue will be coloured according to the first query that it matches (e.g. if your first row first row has query "type = bug" and is coloured red, and your second row has query "assignee = dave" and is coloured green, then bugs assigned to dave will appear red).
Click the Card Colours tab.
In the blue area, choose the colour, type the JQL (see examples below), then click the Add button. For syntax, see the JIRA JQL documentation.
Click the Card Colours tab.
Click in the JQL area, modify the existing JQL and click the Update button. For syntax, see the JIRA JQL documentation.
Some example JQL you might wish to use for your card colours:
Show all issues which belong to a particular component (e.g. 'User Interface'):
project = "Angry Nerds" AND component = "User Interface"
Show all issues which are due in the next 24 hours:
due <= "24h"
Show all issues created by a particular user, e.g.:
reporter = "Jane"
and
reporter = "Bob"
For more details, see the JQL documentation.
16 Comments
Anonymous
Sept 04, 2012Not thrilled with the "performance improvement" of removing the drop down navigation to other boards. Can't this be improved some other way...like not loading until the page load is complete? Adds extra clicks/time to my day, as a portfolio manager.
Anonymous
Sept 04, 2012sorry...posted to wrong page....ignore
Paul Ryan
Sept 05, 2012What permissions are required to change colours? If it's more than a project admin how can we give this capability to individuals for their boards?
Rosie Jameson [Atlassian]
Sept 10, 2012The owner of a board can change colours
Lihi Lutan
Sept 06, 2012I have Greenhopper 6.0.2 but cannot seem to find the tab mentioned here. I'm the board owner and the admin. What can be the reason for that?
Nicholas Muldoon [Atlassian]
Sept 06, 2012Hi Lihi,
That is unexpected, can you please try creating a new board (just a test board) and see if you see the tab there. If you are on 6.0.2 and still do not see the Card Colours tab on that new board please raise a support request.
Thank you Lihi,
Nicholas Muldoon
@GreenHopperTeam
Lihi Lutan
Sept 06, 2012I have a few boards. None of them have it.
I'll raise a support request.
Thanks
Laszlo Kremer
Sept 18, 2012Do you have a list of color codes used for issuetypes in pre 6.0.2 versions?
Martin
Sept 19, 2012Hi Lazlo,
Previously the colours were by issue-type ID, based on a palette of 10 colours which repeated 3 times. Anything outside of issue-type ID 30 would have been the fallback colour.
Fallback colour: rgb(238,238,238)
1, 11, 21: rgb(204,0,0)
2, 12, 22: rgb(255,153,51)
3, 13, 23: rgb(191,228,255)
4, 14, 24: rgb(0,153,0)
5, 15, 25: rgb(0,153,153)
6, 16, 26: rgb(255,214,0)
7, 17, 27: rgb(102,204,51)
8, 18, 28: rgb(204,51,102)
9, 19, 29: rgb(153,0,153)
10, 20, 30: rgb(102,204,51)
The new default palette for issue-types in configurable card-colours is similar for the first 10 issue types (colour 10 was updated since it was unfortunately a duplicate of colour 7) but the following 10 colours are new. The palette is made up of 20 colours and so will start to repeat after 20 issue-types but of course these are now all configurable on the board.
New default colour values for all methods excluding Priority, are as follows:
Fallback colour: rgb(238,238,238);
1: rgb(204,0,0);
2: rgb(255,153,51);
3: rgb(191,228,255);
4: rgb(0,153,0);
5: rgb(0,153,153);
6: rgb(255,214,0);
7: rgb(102,204,51);
8: rgb(204,51,102);
9: rgb(153,0,153);
10: rgb(191,155,30);
11: rgb(141,201,203);
12: rgb(177,71,202);
13: rgb(179,242,144);
14: rgb(204,203,107);
15: rgb(141,104,17);
16: rgb(141,202,253);
17: rgb(182,109,56);
18: rgb(221,78,104);
19: rgb(131,30,7);
20: rgb(136,135,32);
The palette for card colours by Priority will match the JIRA defaults for priority colours.
Laszlo Kremer
Sept 20, 2012Hi Martin,
thanks a lot! We are thinking about the upgrade, and one of the first experience was that che colours are changed. If we decide to upgrade, we'll prefer keeping the existing colours not to make any confusion on the upgrade day.
Cheers,
Laszlo
note: the captcha is hilarious. This is the seventh one and I'm still not able to save the comment. Duh.
Ravi Sagar (Sparxsys)
Jan 14, 2013Is it possible to change the color of the whole card not only the left border but the whole background?
Anonymous
Jan 19, 2013I'm using Greenhopper in the Evaluation phase and I too would like the colour to be the entire background. When shown on the projector, the team can hardly see the colours. I would have thought this request would be Usability 101 so it's very disappointing to find it's not implemented.
Anonymous
Jan 25, 2013+1 for changing the whole background
Chunlei Ding
Feb 21, 2013In classic boards, it is possible to config fields on cards. Is it possible on Rapid Board now? If yes, how?
Thanks a lot!
Johan Holmer Lindell
Apr 26, 2013Same question, how can I add more fields to the cards and detailed views?
One field that I want to see on my cards is number of votes, if there is many votes then I can change ranking easily via drag and drop in this view.
Rosie Jameson [Atlassian]
Apr 28, 2013You can configure the Detail View on the new boards – please see Configuring the Issue Detail View.
Regarding configuring the Cards on the new boards, you may like to watch/vote/comment on GHS-3922 - Getting issue details... STATUS