All Collections
Getting Started
BDD Best Practice
Card Colours With Questions and Ready
Card Colours With Questions and Ready

Using card colours to make questions and ready readable at a glance

Alan Parkinson avatar
Written by Alan Parkinson
Updated over a week ago

This guide is shown mostly for a company-managed, Scrum style project however it will also work for a company-managed, Kanban project using the exact same process.

When using the Questions and Ready feature, you ordinarily will need to view the status of these by going into the detailed view of each individual Jira issue. Instead, you can use Jira's Card Layout features to add colour coding to suit your workstyle. If suiting your workstyle more, would be the use of Swimlanes; you can see at the bottom of the guide, here.

Firstly, you will want to ensure that you have Behave Pro enabled on the specific project. From there, you will want to be on any page with a view of the main board of your project. As shown in the image below, you can find the, "Board Settings".

In Board Settings, you can find the Card colours section, this makes a small stripe on the left side of your Jira issue cards. We will want to base the colours on the JQL that is available with the Questions and Ready feature.

In the example below, we can use the questionCount and readyCount to assign colours to our cards. In this case, if the count of either are greater than one they will be marked with a colour; you may choose a different number depending on the size of your team. You can also use this in conjunction with other JQL variables using the OR or AND option.

In both the backlog and any active sprints, we can now see our stripe of colour on questions that have a ready or question check reaching the numeric value we specified. This allows us to see at a glance whether the team is ready for development to proceed or however else you would like to use these features.

Below is the appearance when this is done on a Kanban style project, all of the options are found in the same location.

Did this answer your question?