Configurable Card Colours for Issue Parameter Visibility
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
How to get the most out of your Boards
Introduction:
JIRA Agile 6.0.2 introduces Configurable Card Colours, a great way to bring important issue parameters into focus. Colours are sensed more rapidly by most viewers than text or numeric information, and can also provide a more full information view when considering a Board as a whole. Plus, they're awesome for wallboards.
We use Story Points as our Estimation Statistic, but we need to know Business Value values to rank issues
This is the classic use case. Business Value drives decisions about evaluating issues, and Story Points are used to 'size' sprints. Business Value is assigned as a Fibonacci value.
How to read Business Value (or other Numeric field) at a glance
For this configuration, we need to see Business Value on the planning board in addition to Story Points to have any idea of which issues are more important. To accomplish this, I configured the Card Colours like so, for maximum pop. You may want to do something similar, using shades of a similar colour instead of different colours:
We need to see Due Dates in the Rapid View
We use the Sprints and Kanban boards in assorted ways, but its very important for planning purposes that everyone be aware of each issue's Due Date as we are using Agile in a very time-sensitive, production environment.
How to Identify Time-Critical Issues at a glance
For this configuration, we need to understand when issues have a near Due Date compared to a more distant Due Date for best Scrum planning.
We can substitute any Date field for duedate, and we can use the pretty date notation (1w 1d 1h 1m) in doublequotes to determine the interval (use a negative value to compare for the past), or we can use JQL Functions. The order of the queries is very important in this case.
We need to visually sort by Component
We need to consider which Components of the project are affected by each issue (or use components for some other project-wide or cross-project sorting).
Components by Card Color
We JQL to sort colors by component. Surprisingly, component names can be used across projects, even if the components have different ID's.
