All JIRA projects contain issues that your team can view, work on, and transition through stages of work — from creation to completion. The path that your issues take is called a workflow. Each JIRA workflow is composed of a set of statuses and transitions that your issue moves through during its lifecycle, and typically represents work processes within your organization.  

In addition, JIRA uses workflow schemes to define the relationship between issue types and workflows. Workflow schemes are associated with a project, and make it possible to use a different workflow for different combinations of project and issue types.

If you need to edit or create a more advanced workflow to match how your team or organization works, you can log in as a  JIRA Administrator  with  global permission to access and create your workflow. Each project in JIRA requires a workflow. If you want to keep things simple you can use the default built-in workflows in JIRA that consist of moving an issue through the basic statuses. Your workflow will depend on which Project types you are using and what workflows have been created in your JIRA application. 

What you can do... Documentation
  • Edit existing workflows
  • Create new workflows
  • Configure existing workflows 

Working with workflows

  • Add a workflow scheme
  • Configure a workflow scheme
  • Managing workflow schemes

Configuring workflow schemes

  • Import and export workflows
  • Activate and deactivate workflows

Managing your workflows

  • Adding custom events
  • Configuring the initial status
  • Working in text mode
  • Configuring workflow triggers
  • Using validators and custom fields
  • Using XML to create a workflow
  • Workflow properties

Advanced workflow configuration

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport