#1 India's Top IT Training Institute
×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
Mentors

Mentors

Meet the industry experts who train and guide you through your course.

Read More →
Free Resources

Free Resources

Free tutorials, interview questions, tools and calculators to help you learn.

Explore →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
Workflow Design

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

Building the Workflow in Jira, Step by Step

The exact menus depend on whether your project is company-managed or team-managed.

Company-managed projects

  1. Go to Settings > Issues > Workflows (Jira administrator access is needed) and add a new workflow, or copy an existing one.
  2. Add the statuses you need and draw transitions between them.
  3. Open each transition to add conditions, validators, post functions and, if needed, a screen to collect fields.
  4. Add the workflow to a workflow scheme and map it to the right issue types.
  5. Associate the scheme with the project. Jira asks you to map existing issues to the new statuses if any old status disappears.

Team-managed projects

Open Project settings > Issue types, pick an issue type and choose Edit workflow. Rules are simpler here, but project admins can change them without asking a Jira administrator.

Worked Example: A Bug Workflow for a QA Team

A team wants every bug to pass code review and QA before it is closed, and wants reopened bugs to return to the developer.

TransitionFrom > ToRule added
Start workOpen > In ProgressPost function: assign to the current user
Send for reviewIn Progress > In ReviewValidator: a linked pull request or fix version is required
Ready for testingIn Review > Ready for QACondition: only developers can move it
VerifiedReady for QA > DoneCondition: only QA group; screen sets the Resolution field
ReopenDone or Ready for QA > In ProgressValidator: a comment is required explaining why

The result is a process that enforces the team's agreements automatically. Nobody can close a bug without QA, and every reopen carries a reason that developers can act on.

Status Categories and the Resolution Field

Every status belongs to one of three categories: To Do, In Progress or Done. Boards, progress bars and many reports use these categories, so placing "Ready for QA" in the Done category by mistake would make unfinished work look complete.

In company-managed projects, the Resolution field is separate from the status. If the final transition does not set it, issues may sit in Done but still appear as unresolved in filters and dashboards. Setting the resolution on the closing transition and clearing it on the reopen transition avoids that confusion.

Design Tips and Pitfalls

  • Keep statuses few. Add a status only when the work truly waits for a different person or decision.
  • Use global transitions carefully. Allowing every status to jump to any other makes the workflow easy to bypass.
  • Test on a copy first. Try the workflow in a sandbox project before switching a busy team over.
  • Update boards afterwards. New statuses must be mapped to board columns, or issues seem to vanish.
  • Document the rules. A short note in the project explaining who can move what saves many questions.

Before publishing: walk one sample issue through every path, including reopen, as each type of user, and confirm that fields, permissions and notifications all behave as planned.

Master Jira with Expert-Led Training

Hands-on classes, mentor support, and placement assistance — all in one course.

Explore Jira Course