• Products
  • Documentation
  • Resources

Customize cards

This page applies to company-managed projects only.

Learn more about the difference between company-managed and team-managed projects.

Before you begin

To configure the board and any of its settings, you must be either:

  • project administrator for the location of the board

  • board administrator for the board itself

Learn more about permissions in Jira Software Cloud.

Why customize cards

By customizing the layout of the cards on your board, you're bringing just the right level of information to your team's attention, at a glance. You can:

  • Change the card colors to help your team quickly identify the cards on your board as being of a particular issue type, priority, assignee, or anything you choose

  • Add up to three custom fields to display on the cards

The default card layout

Issue cards have three layers of information that are stacked on top of each other following this pattern —

  1. The issue summary is always at the top on the board and backlog.

  2. Any custom fields added to the card are next.

  3. Then details about the issue, including issue type, priority, assignee, and estimate.

To view all other fields, select a card to open the issue detail view.

Configure card colors

You can base your card colors on issue types, priorities, assignees, or JQL. Colors are configured per board (not globally).

To add color:

  1. If not already there, navigate to your company-managed project.

  2. Select Active sprints(if you use a Scrum board) or Kanban board (if you use a Kanban board).

  3. Select More () > Configure board.

  4. Select Card Colors and Select method from the drop-down.

  5. Select the square in the Color column, and pick a color for the issue type, priority, assignee, or query. You can switch between methods, and your settings will be retained.

Some colors are no longer available in the new color picker. For assignees and issue types, select Remove to update your choice.

Priority colors can be Reset to global color, that are defined in Settings > Issues > Priorities.

To edit or remove colors from a query, select More [], then:

  1. Edit the card color or update the query.

  2. Delete the card color to remove the color and make it usable for other queries. Any issues that used that color will restore to the default when you reload your page.

  3. Reorder a card color by dragging and dropping the dotted grid icon [] to a new position.

For query-based colors, the order is important as each issue will be colored according to the first query it matches.

For example, if your first row has the query "issuetype = bug" and is colored red, and your second row has query "assignee = kevin" and is colored green, then bugs assigned to Kevin will appear red.

For each method, you can apply one color for item. For example, pick one color for each issue type, priority, assignee, or query.

The colors display as a thin strip on the left-side of the cards on your board.

Method

How it works

Issue types

First create an issue on your board, then pick a color for your issue types.

A default color will be allocated to all existing issue types. The default issue types and colors are:

  • Task = blue

  • Sub-task = light-blue

  • Bug = red

  • Story = purple

Priorities

The default priority colors match the default colors for priorities across Jira.

Assignees

First create an issue on your board, then pick a color for your assignees.

A default color will be allocated to every user who’s ever been an assigned an issue on your board.

Queries

You can choose to add a color to any query. Issues that don't match your JQL queries will be shown in grey. Read more about JQL syntax

Sample queries

Show all issues that are due in the next 24 hours

1 due <= "24h"

Show all issues created by a particular user

1 reporter = "Jane"

Show all issues due by the end of month

1 duedate > endOfMonth()

Adding fields to cards

You can configure cards on a board to display up to three additional fields. The fields can be different for the backlog and Active sprints, if you are using a Scrum board.

To add fields to cards:

  1. If not already there, navigate to your company-managed project.

  2. Select Active sprints (if you use a Scrum board) or Kanban board (if you use a Kanban board).

  3. Select More () > Configure board.

  4. Select Card layout.

  5. Add or delete fields as desired.

You can also enable Days in column to visually indicate how long an issue's in a column. This helps identify slow moving work.

Using days in column

This is automatically enabled for Kanban boards and disabled for Scrum boards.

If you have a large instance (more than 300,000 issues, 100 projects, 100 boards, or 100 open sprints), we recommend you disable this indicator to improve performance.

When you enable Days in column you’ll see a series of dots on each issues to represent the number of days it’s been in that column (and essentially, status).

This helps you see if issues are stagnating and is particularly useful when your board is displayed as a wallboard.

Dots in cards

Number of days in column

A single grey dot, representing 1 day.

1 day

Two grey dots, representing 2 days.

2 days

Two grey dots and one yellow dot, representing 3 days.

3 days

Three grey dots and one red dot, representing 5 days.

5 days

Two grey dots and two red dots, representing 8 days.

8 days

One grey dot and three red dots, representing 12 days.

12 days

Four red dots, representing 20 or more days.

20 or more days

If you move an issue to a column where it's previously been, the indicator provides the cumulative number of days that the issue has been in that column.

For example, you move an issue to the In progress column, and it stays there for two days.

You then move the issue to the Code review column, and it stays there for one day.

During code review, you receive feedback, which requires more development work. So, you move the issue back to the In progress column, and it stays there for one day.

In this example, the dots will reflect the cumulative value — which was three days — that the issue was in the In progress column.

Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting help.

Additional Help