Card automations are now live in Kanban Studio

Context

Today we are announcing a completely new feature in the app: card automations. There was no previous automation implementation, so this release opens a new way to operate inside your boards. The goal is not just to save clicks. The goal is to reduce coordination noise and make board behavior more predictable when teams are shipping fast.

Many teams told us they had a repeat pattern every week: move a card, assign a person, add a due date, write the same reminder, and repeat across dozens of tasks. When this process depends on manual discipline, quality drops over time. Card automations help us remove that fragile layer.

What changed

• You can now define automations to execute actions without manual repetition on every card.
• We included initial triggers that cover common operational workflows.
• Configuration is managed directly inside the card experience.
• Rule execution is visible in card history so teams can audit what happened.

The release starts with a focused rule set because reliability matters more than feature count. We are prioritizing stable behavior before we add more combinations.

Practical examples

Here are three patterns teams are already testing:

1. When a card enters In Progress, assign the owner and start an internal timer.
2. When a card is moved to Review, notify the reviewer and add a checklist template.
3. When a due date is updated, post an activity note so everyone sees the timeline change.

These are small actions, but the impact compounds when your board has real daily traffic.

Impact for teams

This launch reduces repetitive work from the first use. Teams get more consistent execution, fewer follow-up misses, and more time to focus on high-value work. It also creates better team alignment because every automation leaves traceable events in one shared timeline.

Try it now

You can go to your board and test it in your real workflow:

Go to board

Enable one automation on a card, run it in a real project, and share feedback about where the current rule set helps or where it still falls short.

Related references

• Atlassian automation overview
• Notion database automations

Next step

We will expand available triggers and actions so each team can adapt automations to how they actually work. The next iterations will focus on safer multi-action flows, better conditions, and clearer debugging for failed runs.