Add and change card types

Rename the kinds of card, add your own, choose the default and understand behavior.

In short

Every card has a type, such as Task, Bug, Story or Epic. You can rename types, recolor them, add your own and choose the default. A type's behavior - plain task, bug or story - decides what extra fields its cards have.

Before you start

Who: only people who manage the board change card types ("Create and manage boards").
Plan: every plan.
First: decide the behavior. It cannot change once any card uses the type.

Steps

Open Board settings, then "Card types" ("What does a card hold?").
Rename a type, pick its color and icon, or reorder the types.
Choose "Add type" to add your own, or "Make default" on the type new cards should start as.

Result: the new name or color shows on every card of that type at once.

Good to know

Simple tasks, Software delivery, Bug tracking and IT requests boards start with Task, Bug, Story and Epic. Other layouts start with Task and the type for their kind of work, such as Goal, Campaign, Deal, Post or New hire.
Renaming bugs to Defects changes the label on every card and nothing else.
Bug behavior gives a card a severity, a triage state and fix and verify steps; Story behavior a business description and acceptance criteria. A type you add starts with plain Task behavior.
To create a bug or story, use its own flow rather than retyping a task.
A type can be marked as a root type, where the rollup of child cards stops.
Changing card types needs the manage permission on the board.
Defaults: new cards start as the default type. A type you add starts with plain Task behavior.
What happens next: a new name or color shows on every card of that type at once. Deleting a type moves its cards to another type with the same behavior.

If something goes wrong

"A card can only change between types with the same behavior. Create a Bug or Story through its dedicated workflow."
"Choose another default card type before removing the current default."
"Cards of this type need another" type with the same behavior to move to: add one before deleting this type.
"A card type's behavior cannot change after it has been used."
"A board must have at least one card type.": a board keeps at least one, so add another before you delete the last.