Blog ·

Jira workflow examples: seven workflows you can copy today

Looking for Jira workflow examples you can actually use? Below are seven, each written out as its statuses, the transitions between them, and the one or two rules that make it work: a bug workflow, a feature workflow, a service request workflow, an approval workflow, a release workflow, a content workflow, and a recurring maintenance workflow. Copy the one closest to your team, delete the statuses you will never use, and keep it short. The best Jira workflow is usually the smallest one that still tells you where every piece of work is.

Statements about Jira Cloud are as of October 2026, from Atlassian's own documentation. Atlassian now calls an issue a work item and a project a space. This guide uses the older words where most admins still do.

What a Jira workflow is #

Atlassian's documentation defines it in one sentence:

A Jira workflow is a set of statuses and transitions that a work item moves through. It typically represents a process within your organization.

Statuses are the steps. Transitions are the allowed moves between them. A workflow is attached to a project, and optionally to specific issue types, through a workflow scheme. Jira ships built-in workflows you cannot edit, but you can copy one and change the copy.

Every status also belongs to a category: To Do, In Progress or Done. Boards, reports and filters lean on those categories, so a custom status like "Waiting on vendor" should sit in the category that matches what it means for the work. Waiting is still in progress.

Who can change a workflow depends on the project type. In a company-managed project it is site admins and people with the edit workflows permission; in a team-managed project it is site admins and project admins.

The seven examples at a glance #

Example Statuses Best for Key rule
Bug Open, In Progress, In Review, Done, Won't Fix Software teams Resolution required on close
Feature Backlog, Selected, In Progress, In Review, Done Product and dev teams Only selected work can start
Service request Waiting for Support, In Progress, Waiting for Customer, Resolved IT, HR, facilities Reply moves it back automatically
Approval Draft, Pending Approval, Approved, Rejected, Done Purchases, access, changes Only the approver can approve
Release Planned, In Development, Code Freeze, Released Release managers Freeze blocks new scope
Content Idea, Writing, Editing, Scheduled, Published Marketing and comms Due date required to schedule
Recurring maintenance To Do, In Progress, Done, Skipped Ops, finance, compliance A new one appears each cycle

Example 1: a bug workflow #

Statuses: Open → In Progress → In Review → Done, with a side exit to Won't Fix.

Rules worth adding:

Keep the bug workflow separate from the feature workflow if your bugs need triage and your features need planning. Our Jira QA testing guide covers the testing side of the same cycle.

Example 2: a feature workflow #

Statuses: Backlog → Selected for Development → In Progress → In Review → Done.

The extra status here is Selected for Development. It separates "we might do this" from "we have agreed to do this next", which is the difference a planning meeting exists to make.

Rules worth adding:

This pairs well with the board setup in Jira kanban board and the planning rhythm in Jira sprint planning.

Example 3: a service request workflow #

Statuses: Waiting for Support → In Progress → Waiting for Customer → Resolved.

This is the shape most request desks end up with, whether the requests are laptops, payroll questions or a broken door badge. The important status is Waiting for Customer, because it is where requests stall without anybody noticing.

Rules worth adding:

Jira for IT operations and Jira for HR show this workflow inside a full team setup.

Example 4: an approval workflow #

Statuses: Draft → Pending Approval → Approved or Rejected → Done.

Use it for anything that needs a yes before work starts: a purchase, an access grant, a change to production.

Rules worth adding:

For the change management version with fields and a full flow, see Jira change management template.

Example 5: a release workflow #

Statuses: Planned → In Development → Code Freeze → Released.

This one usually tracks a release ticket or an epic, not every story inside it. Each status marks a phase the whole team needs to know about.

Rules worth adding:

The steps that happen at each release fit better as a checklist than as statuses. Jira release checklist explains where those steps should live.

Example 6: a content workflow #

Statuses: Idea → Writing → Editing → Scheduled → Published.

Marketing and comms teams get a lot from Jira once the workflow matches how a piece actually moves. Scheduled is the status that earns its place: the piece is done and waiting for its date.

Rules worth adding:

Jira for marketing covers the board and the routine around this workflow.

Example 7: a recurring maintenance workflow #

Statuses: To Do → In Progress → Done, with a side exit to Skipped.

This is the workflow for work nobody reports: the monthly access review, the quarterly backup restore test, the weekly dependency update, the month-end report. It looks simple because it is. The hard part of recurring work is never the workflow. It is making sure the issue exists in the first place.

Rules worth adding:

Getting a new issue into the workflow every cycle #

There are three ways to do it, covered in depth in Jira recurring tasks:

  1. Clone last cycle's issue by hand. Free and fine for one or two chores, until the person who remembers goes on leave.
  2. A scheduled Jira Automation rule that creates the issue. Flexible, and each run counts toward your plan's automation usage; Jira Automation pricing explains how.
  3. A scheduling app. Recurring Work Items for Jira is ours. A rule is a schedule plus an issue template, written once in one project: daily, weekly, monthly or quarterly, with working-day and holiday handling, titles built from date tokens, and subtask checklists. It uses no Jira Automation quota, and every run, created, skipped or failed, is written to the rule's history with the reason.

Whichever way the issue is created, it then moves through the maintenance workflow above like any other issue.

How to build any of these in Jira Cloud #

  1. Open the project's settings and find Workflows.
  2. Copy the built-in workflow closest to your example rather than starting empty.
  3. Add the statuses you need and put each in the right category.
  4. Draw the transitions. Leave out any move you do not want people to make.
  5. Add the rules (conditions, validators, post functions) on the transitions that need them.
  6. Publish, and attach the workflow to the issue types it is for.

Test it with a throwaway issue before announcing it. Moving one issue through every transition takes two minutes and finds the missing arrow before the team does.

Common mistakes with Jira workflows #

For enforcing rules on transitions and reacting to events around them, see Jira workflow automation. For keeping the board clean once the workflow is live, see Jira hygiene.

When the built-in workflow is enough #

Plenty of teams never need a custom workflow. If your work goes from "not started" to "started" to "finished" and nobody needs an approval or a review step, the default To Do, In Progress, Done is the right choice. Add a status only when someone keeps asking "where is this?" and the answer is a step the board does not show.

Frequently asked questions #

What is a simple Jira workflow example? To Do → In Progress → Done. It is the default for a reason and fits most small teams.

What is the best Jira workflow for software development? Usually a feature workflow like Example 2 plus a bug workflow like Example 1, with In Review in both so code review is visible on the board.

Can a Jira workflow create issues on a schedule? No. A workflow moves issues that already exist. Recurring issues come from a scheduled Automation rule or an app such as Recurring Work Items for Jira.

Who can edit a workflow in Jira Cloud? Site admins, plus people with the edit workflows permission in a company-managed project, or project admins in a team-managed one.