Create ticket visual indicators

Visual indicators are configured on board card field blocks. They evaluate ticket values and render badges, colored text, dots, arrows, progress bars, chips, or avatars on the card.

Use them when a reviewer should notice a condition without opening the ticket.

Choose the field to visualize

1. Open the project.
2. Select Boards.
3. Edit the saved board.
4. Go to Card layout.
5. Add or select the field block you want to visualize.

Good fields for visual indicators:

• Priority.
• Progress.
• Due date.
• Status.
• Assignee.
• Labels.
• Custom fields such as severity, customer tier, risk, reviewer, environment, or launch phase.

Start from a preset

1. With the field block selected, open Style.
2. Choose Custom local style.
3. In Start from a preset, pick a preset that matches the field:
   • Dots for level or health.
   • Arrows or Stacked chevrons for priority.
   • Traffic light for severity or risk.
   • Overdue red for due dates.
   • Progress health for progress.
   • Avatar only for user fields.
4. Continue to the visual rule editor.

Presets are starting points. Adjust thresholds, colors, text, and fallback behavior before saving.

Configure the display

1. Enter a Style name.
2. Choose Display:
   • Indicator for compact symbols.
   • Badge for compact labeled values.
   • Colored text for subtle emphasis.
   • Progress bar for progress fields.
   • Chips for labels or multi-select values.
   • Avatar or Pill for user fields.
3. If using avatar display, choose avatar-only, avatar plus name, or avatar stack.

Choose the display that supports scanning. Do not use bright indicators for every field.

Add visual rules

1. Select Add rule.
2. Choose the operator, such as =, between, overdue, within next N days, is one of, or contains any.
3. Enter the value or threshold.
4. Choose the rule color.
5. Choose whether to show a value, custom text, glyph, or hide text.
6. Add more rules in priority order.
7. Move rules up or down so the most specific condition is checked first.

Example priority rules:

When	Variant
Priority <= 1	Red, three chevrons up
Priority = 2	Orange, two chevrons up
Priority = 3	Yellow, one dot
No match	Neutral text

Example due date rules:

When	Variant
Overdue	Red badge
Today	Orange badge
Within next 7 days	Yellow colored text
No match	Muted text

Set the fallback

1. Find If no rule matches.
2. Choose the fallback color, icon, and text mode.
3. Use a neutral fallback for normal values.
4. Preview with a sample value.

The fallback should keep normal tickets readable without making them look urgent.

Save for one board or reuse across boards

Use a local style when only this board needs the indicator:

1. Leave the style as Custom local style.
2. Save the board.

Create a reusable project style when multiple boards need the same indicator:

1. Enter a clear style name.
2. Select Save as project style or Save style.
3. Confirm the selected field block now uses the saved style.
4. Reuse that style on other boards with the same field.

Project styles are field-specific. A priority style will not automatically apply to a due-date field.

Verify the indicator

1. Select Preview card.
2. Refresh the board preview.
3. Check cards with different values.
4. Confirm urgent cards stand out and normal cards stay calm.
5. Save the board.
6. Open Tickets and review the board with real work.

Maintain indicators

Review visual indicators when:

1. Priority meaning changes.
2. New custom-field options are added.
3. A field is renamed, archived, or restored.
4. Reviewers misread the symbol.
5. Too many cards look urgent.

Related guide: Design board cards.