How to use conditionals to show different information and buttons on the card cover depending on the stage
In Jestor's kanban, the card cover — the part visible from the outside, without opening the record — accepts conditionals to decide which fields and which buttons appear, depending on the stage or any other condition.
Why do conditionals on the card cover matter?
Always showing the same fields and buttons on the card cover, at every stage of the process, clutters the kanban — an approval button that only makes sense at a specific stage stays visible even at stages where it shouldn't appear at all.
How to configure conditionals on the card cover?
- Card cover conditional settings sit alongside color conditionals and open-card conditionals, in a specific "fields shown on the card" option.
- You can decide whether each field or button appears or disappears based on a condition — by stage, or by any other criterion, like a value above a certain threshold.
- Buttons are also conditional: a cancel or approval button can appear only at the stage where that action makes sense.
- This helps prevent operational mistakes, like approving a card at the wrong stage.
- Worth noting: this conditional is about usability, not permissions.
| Conditional element | Example rule |
|---|---|
| Displayed field | Only show the value if it's above a certain threshold |
| Action button | Only appear at the stage where the action makes sense |
To configure conditionals on the card cover:
- In the kanban editor, open the conditionals section.
- Choose "fields shown on the card."
- Define the condition — stage, field value, etc.
- Select which fields or buttons appear when the condition is met.
Why choose Jestor to keep the kanban more organized?
With the card cover showing only what's relevant at each moment, the kanban stays cleaner and fits more useful information on the same screen.
Frequently asked questions
Does this conditional only work by stage?
No, it can be configured by any criterion, like a field value above a certain threshold.
Can action buttons also be conditional?
Yes, a button can appear only at the stage where that action makes sense.
Does this replace the permission rules for who can view or edit a card?
No, it's a usability conditional, not a permission one.
Do I need automation to prevent someone from approving at the wrong stage?
Not necessarily — the display conditional already reduces that risk by hiding the button outside its proper context.
Reference video
Check out the Jestor YouTube channel for more content like this.
Discover Jestor
With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.