Managing your workflows

Still need help?

The Atlassian Community is here for you.

Ask the community

As a Jira administrator, you need to activate workflows before your teams can use them to streamline project work. To activate a workflow, include it in a workflow scheme and associate that workflow scheme with a project. You can also import and export workflows to share them across teams. 

Before you begin. This page contains information for how to set up and configure classic Jira projects. Classic Jira projects have different features and capabilities than next-gen Jira projects.

If you're looking for information on setting up a next-gen project, check out the following documentation:

Activating a workflow

All workflows are inactive until you associate them with a workflow scheme, which can then be associated with a project. To activate a workflow: 

  1. Select > Issues.
  2. Under WORKFLOWS, click Workflow schemes to see a list of active and inactive schemes. 
  3. Create a workflow scheme or edit an active workflow scheme. Tip: click the Active or Inactive headings to expand and collapse the list of workflows.
  4. Add your workflow to the scheme. See Configuring workflow schemes for more information. 

  5. Follow the steps in the Associating a workflow scheme with a project section below.

Associating a workflow scheme with a project

To finish activating your workflow, associate the workflow scheme it's in with a project. If an issue type is not defined in the project's issue type scheme, that specific workflow is not used.

  1. Choose Settings > Projects.
  2. Select the project you want to associate your workflow scheme to.
  3. Go to your project and click Project settings
  4. Click Workflows. You'll see which workflow scheme the project currently uses.
  5. Click Switch Scheme and select the relevant workflow scheme from the Scheme list. 

  6. Click Associate to begin the migration process. Each issue needs to have a valid status, so you may need to assign statuses to a select number of issues after you switch workflow schemes. 

A Jira project must always be associated with a workflow scheme, since all issues must move through a workflow. To disassociate a custom workflow scheme from a project, simply associate that project to the default workflow scheme instead.

Importing a workflow

  1. Select > Issues.
  2. Select Import from Marketplace.
  3. Find the workflow you want and click Select.
  4. Map the steps of the workflow to your existing workflow statuses or create new statuses at this point. When you are finished, click Next to continue.
  5. Preview your changes and click Import

Exporting a workflow

  1. Select > Issues.
  2. Under WORKFLOWS, select Workflows
  3. Find the workflow you want to share and click View.
  4. Select Export > As Workflow and click Next to continue.
  5. Add any special configuration notes (for example, information about plugins that should be installed).
  6. Click Export and select a download location. Ensure the location is publicly accessible.

Exporting a workflow to Atlassian Marketplace

  1. Create an account on Atlassian Marketplace.
  2. Log in to the Atlassian Marketplace and choose Manage Add-ons. See Step-by-step Paid-via-Atlassian Listing for more information. 
  3. Click Create new add-on.
  4. Choose My add-on is not directly installable and make sure the add-on type is "not a plugin". 
  5. Add information about where the workflow export can be accessed in the Binary URL section.
  6. When you fill out the submission form, be sure to note the following:
    1. The Summary field contains the information that will be displayed to users searching the Marketplace. 
    2. The Category for your workflow must be Workflow Bundles to ensure that it's visible to other Jira application users.
    3. The Add-on Key, which becomes your application URL and identifies your application, must be unique.

You don't have to complete the form in one session. You can save your form and come back to it later. Once you accept the Atlassian Marketplace Vendor Agreement, the system submits your add-on for review by Atlassian's Developer Relations team.

Last modified on Aug 26, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.