GreenHopper is now called JIRA Agile. Learn more.

Skip to end of metadata
Go to start of metadata

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.

On this page:

Related pages:

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.

PrioritiesOne colour per priority. The default colours are the same as used for priorities in JIRA.
AssigneesOne 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).

(info) Note that only the administrator of a board (or a person with the 'JIRA Administrators' global permission) can configure a board's card colours.

Choosing a different method of card colouring

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. Click the Card Colours tab.
  3. 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.

  4. 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.

 

Changing a card colour

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. Click the Card Colours tab.

  3. 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.

 

Deleting a card colour

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. Click the Card Colours tab.

  3. Click the Delete button for the colour that you wish to delete.
    (warning) 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.

Moving a card colour

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. Click the Card Colours tab.

  3. Hover over the vertical 'grid'  icon, then drag and drop the colour up or down to its new position.

(warning) 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).

Adding a Query-based card colour

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. Click the Card Colours tab.

  3. In the blue area, choose the colour, type the JQL (see examples below), then click the Add button.
    (info) For syntax, see the JIRA JQL documentation.

  4. If more than one query matches a card, the first query that matches will be the color that is used. 

Changing a Query

  1. Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
  2. Click the Card Colours tab.

  3. Click in the JQL area, modify the existing JQL and click the Update button.
    (info) 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'):

  • Show all issues which are due in the next 24 hours:

  • Show all issues created by a particular user, e.g.:

    and

(info) For more details, see the JQL documentation.


 

 

9 Comments

  1. When can we expect the same functionality from the classic board, when we could add more fields to a card?
    We also use JIRA agile to visualise all the ongoing projects on an overall level and would like to add information like "Project manager", "Tech lead" etc on the cards.


    I´ve raised this as a issue (see issue GHS-9855) to see if some of the developers find it interesting (wink)

    1. I agree with Mikael. We would like to add information about remaining hours and assignee to our virtual Kanban board cards. 

    2. Hi Mikael,

      Can you post the URL of the ticket?

      1. Hi

        Here's the URL to my ticket:
          GHS-9855 - Add fields to cards on scrum/kanban boards Resolved
        However, I just saw it was closed and treated as a duplicate of  GHS-3922 - As a user, I would like to configure the cards displayed in the rapid board Open
        GHS-3922 seems to adress card features on a much broader level and is filled with alot of interesing feature requests.

         

        Regards,
        Mikael 

  2. I found that when coloring the tickets with JQL the rapid board would be extremely slow to load (30+ seconds). Is this a known problem/behavior? Also, is it linear with the number of coloring queries?

  3. In our shop the card color is based on the assignee.  Is there a way to assign a card color to a user so that is global across all boards/projects?

    1. This is currently a per board configuration option.

      Regards,

      Martin
      JIRA Agile team

  4. Wow, I just realized that you can only change card colors if your project already has issues created of that type. i.e., setting up a new board for a new project, you can't change Story card colors unless you have a Story created. Same thing for Task, Bug, etc. Can we get that fixed?

    1. The management of the card colours checks for the presence of items which may need a configuration. This was considered the simplest and most convenient way to manage the configuration. It's unlikely we'll be revisiting this as usually the issue types are present.

      Regards,

      Martin
      JIRA Agile team