Creating Custom Workflows

A Jira workflow defines the exact statuses an issue moves through and the transitions allowed between them. While Jira ships with default workflows, most teams eventually need a custom workflow that reflects how they actually get work done.

Designing a Workflow

Building a custom workflow starts with mapping out your team's real process on paper: what statuses exist, in what order work typically moves, and where approvals or reviews are needed. From there, you recreate that map inside Jira's workflow editor using statuses and transitions.

Adding Rules and Conditions

Custom workflows can include conditions that control who can perform a transition, validators that check required fields before an issue moves forward, and post functions that trigger actions automatically, such as assigning an issue when it moves to 'In Review'.

Building Blocks of a Custom Workflow

• Statuses that represent each stage of work
• Transitions that connect one status to another
• Conditions that control who can trigger a transition
• Validators that enforce required fields before moving forward
• Post functions that automate actions after a transition