How to Set Up Custom Workflows in Jira (Company-Managed and Team-Managed)
Jira's default workflow is a reasonable starting point, but it rarely matches how a team actually moves work from idea to production. Teams end up with statuses that nobody uses, missing steps such as code review or QA, and boards that do not reflect reality. A well-designed workflow makes the board an accurate picture of the work and gives PMs reliable data on where things stall.
Jira has two project types with different workflow models. Company-managed projects use shared workflows and workflow schemes managed by Jira admins. Team-managed projects let project admins edit workflows per issue type directly. This guide covers designing the workflow first, then configuring it in either project type, and finally mapping it to your board.
Working in Jira? Turn your spec into dependency-ordered tickets.
Paste the feature or spec. Vantage pulls out the requirements and breaks them into tickets, ordered by what blocks what, ready to groom with your team.
How this works
- We save what you typed. No AI runs on this page.
- You create a free account.
- Vantage builds a PRD and dependency-ordered tickets from it inside your own workspace.
Why ask for an account? We’re a small team, and a full generation runs a multi-step AI pipeline that costs us real money. So we tie it to a free account instead of running it anonymously. You also get to keep the result and edit it.
Your text is only used to create your project, and it stays private to your account. If you don’t sign up, we delete it after 7 days. Privacy policy
Step-by-step guide
Map the real process before touching Jira
Write down the steps work goes through today, from the moment it is ready to start until it is in customers' hands. Talk to engineers and QA, not just the team lead. Each step that involves a handoff or a wait is a candidate status. Each step that is just an activity within someone's work usually is not.
- List each stage work passes through, including handoffs
- Mark where work commonly waits, such as review or QA
- Remove stages that exist only on paper
- Aim for five to eight statuses in total
Assign each status to a status category
Every Jira status belongs to one of three categories: To Do, In Progress, or Done. Categories drive reporting, board coloring, and JQL like statusCategory = Done. Make sure statuses that represent finished work, such as Released, are in the Done category, and that waiting states such as In Review are In Progress.
Configure the workflow in a company-managed project
Jira admins manage workflows from the Jira settings area for issues, under Workflows. Copy an existing workflow rather than editing the default, add your statuses, and draw transitions between them. Transitions can have conditions (who can move an item), validators (what must be true, such as a field being filled in), and post functions (what happens automatically after the move). Then associate the workflow with issue types through a workflow scheme, and assign that scheme to the project.
- Copy an existing workflow and give it a descriptive name
- Add statuses and transitions that match your process
- Add validators for required fields at key transitions
- Associate the workflow with issue types in a workflow scheme
- Assign the workflow scheme to the project and map existing statuses
Configure the workflow in a team-managed project
In team-managed projects, go to Project settings, open the issue type you want to change, and edit its workflow. You can add statuses, set transitions, and add rules such as restricting who can make a transition or requiring a field. Each issue type has its own workflow, so a Bug can go through a triage step that a Story skips.
- Open Project settings and select the issue type
- Edit the workflow to add or rename statuses
- Add transition rules where you need control
- Repeat for each issue type that needs a different flow
Handle existing issues when statuses change
When you remove a status or switch a project to a new workflow, Jira asks you to map issues in old statuses to new ones. Plan this mapping in advance, especially for large projects, and communicate the change so people are not surprised to see work move columns.
Map statuses to board columns
A new status does not automatically appear where you expect on the board. Open the board settings, go to Columns, and map each status to a column. Statuses left unmapped are hidden from the board. Consider whether multiple statuses should share a column, for example a single 'Review' column holding both Code Review and Design Review.
Add automation for repetitive transitions
Once the workflow is stable, use Jira automation to handle routine moves: transition an issue to In Review when a linked pull request is opened, or to Done when it is merged, if you use a development tool integration. Automation keeps the board accurate without asking engineers to update status by hand.
Common mistakes
Too many statuses
A fifteen-status workflow guarantees that items sit in the wrong column. Every status should represent a real, distinct state that someone acts on.
Editing the shared default workflow
In company-managed Jira, changing a workflow used by many projects affects all of them. Copy it and create a project-specific workflow instead.
Forgetting to update board columns
New statuses that are not mapped to a column disappear from the board, which looks like lost work. Always check column mapping after workflow changes.
Tips
Add a validator requiring acceptance criteria before work moves to In Progress.
Use a single 'Blocked' flag or status consistently across projects so blocked work is easy to report on.
Document the meaning of each status in the project's description or wiki page.
Review cycle time per status after a month to see where work actually waits.
How Vantage helps
A clear workflow matters most when tickets arrive well-formed. Vantage generates dependency-aware tickets from your PRD, with acceptance criteria and sequencing included, and is building Jira as a first-class ticketing target alongside Linear so the spec and the work stay connected.