Managing your workflows
Workflows need to be activated to use them in JIRA. Activating a workflow is the process of mapping the workflow to a workflow scheme, and then associating the workflow scheme with a project. To configure a workflow scheme, see Configuring workflow schemes.
A workflow scheme defines a set of associations – or mappings – between a workflow and an issue type. Workflow schemes are associated with a project and make it possible to use a different workflow for every combination of project and issue type.
For all of the following procedures, you must be logged in as a user with the JIRA Administrators global permission.
On this page:
Activating a workflow
Active workflows are those that are currently being used, while inactive workflows are those that are not associated with any workflow schemes, or are associated with workflow schemes that are not associated with any projects. Active workflow schemes are also those associated with projects, while inactive workflow schemes are not.
- Create a workflow scheme or find an existing workflow scheme. See Configuring workflow schemes for instructions.
Configure the workflow scheme to use your workflow. See Configuring workflow schemes for instructions.
Associate your workflow scheme with a project, as described in the Associating a workflow scheme with a project section below.
Managing workflows for projects
You can manage your workflows by associating workflow schemes, importing, exporting, uploading, and sharing.
Associating a workflow scheme with a project
You can associate a single workflow scheme with more than one project, although only one workflow scheme can be associated with a given project. The issue type scheme associated with a project defines the issue types that are available to that project. If an issue type is not defined in the project's issue type scheme, its workflow is not used.
- Choose > Projects. The Project Summary page is displayed.
- Click Workflows on the left of the Project Summary page (you can also click the More link in the Workflows section in the middle of the screen). This is the current workflow scheme used by the project.
Click the Switch Scheme link to display the Associate Workflow Scheme to Project page.
Select the relevant workflow scheme from the Scheme list and click the Associate button to begin the migration process.
Each issue has to be in a valid status. The valid statuses for an issue are defined by its workflow. This means that when changing a workflow, you may need to tell JIRA the status for specific issues after the change.
- A screen displays that indicates the progress of migrating all the project's issues to the updated scheme's workflows. Acknowledge to finish the process.
Disassociating a workflow scheme from a project
A JIRA project must always be associated with a workflow scheme, since all issues must move through a workflow, even if that workflow only consists of a single Create Issue transition. By default all JIRA projects with unmodified workflows use JIRA's system workflow. Disassociating a workflow scheme re-associates your project's workflow with JIRA's default workflow scheme.
- Follow the instructions in Associating a workflow scheme with a project above.
- When selecting the workflow scheme from the Scheme list, select the Default workflow scheme
- Click the Associate button, and follow the wizard, which guides you through migrating all of the project's issues.
Exporting your workflow
The workflow sharing feature allows you to share your team's workflow with other teams in your organization on different JIRA instances, or external parties in other organizations via the Atlassian Marketplace. This feature allows you to easily share and use workflows that other people have published, or to move a workflow from staging to production in your own organization. you wish to share your JIRA Workflow with another instance of JIRA or upload it to the Atlassian Marketplace, you first need to download it.
- Choose > Issues.
- Find the workflow you wish to share by clicking on the Workflows section in the left-hand panel.
- Click View or Edit under the Operations column.
- Select Export > As Workflow and click Next to continue.
- In the Add Notes field, add any special configuration notes; for example, information about plugins that should be installed. JIRA auto-populates these notes for you when it discards parts of your workflow (for example, plugins, post functions, conditions, validators).
Click Export and select a download location. Ensure the location is publicly accessible.
Uploading to Atlassian Marketplace
To share your workflow with other JIRA users, upload it to the Atlassian Marketplace.
- Create an account on Atlassian Marketplace, or log in and choose Manage Add-ons (more info: Step-by-step Paid-via-Atlassian Listing).
- Click Create new add-on.
- Choose My add-on is not directly installable (ensure that 'Add-on Type' is listed as 'Not a Plugin').
You will need to host the workflow on your own servers, and add information about where the workflow export can be accessed in the Binary URL textbox. This should be the location you specified in step 6 of the prior instruction set.
- Fill out the submission form, be sure to note the following:
- The Summary field contains the information that will be displayed to users searching the Marketplace.
- The Category for your workflow must be Workflow Bundles. Choosing Workflow Bundles ensures other JIRA users will have visibility to your workflow.
- The Add-on Key must be unique, as it uniquely identifies your application; it will become the application URL.
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.
Custom fields in workflow imports
If your workflow contains custom fields that are disabled, the workflow importer will not create these fields unless they are enabled before importing. You will receive a warning about this. To fix this, you need to enable the missing custom fields before proceeding with the import.
- Click on the highlighted Custom Field Types & Searchers plugin in the displayed warning. This opens the plugin in a new window and scrolls to the right place to make the necessary changes.
- Click to expand the list of enabled modules.
- Find the modules that are disabled and enable them.
After enabling the corresponding modules of the Custom Field Types & Searchers plugin, return to the summary page and proceed. You may need to refresh the page first. For information on installing add-ons, see Viewing installed add-ons.
Importing from Atlassian Marketplace
This procedure covers importing a workflow from Atlassian Marketplace.
- Choose > Issues.
- Click on the Workflows section in the left-hand panel.
- Select Import > Import Workflow in the top right of the screen.
- The From Atlassian Marketplace option should be selected by default.
- Find the workflow you want and click the Select button.
- Follow steps 5 through 8 of the Importing from a local instance procedure.
Importing from a local instance
This procedure covers importing a workflow from a local instance. You must be logged in as System Administrator to perform this function.
- Click on the Workflows section in the left-hand panel.
- Select Import > Import Workflow.
- Select a workflow from your computer to upload, and then click Next.
- JIRA automatically generates a workflow name, but you can change this if you like. Click Next.
- Next, you are presented with a screen that details your workflow statuses, as shown below. You can 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.
- At the Preview of Import screen, click Import at the bottom of this screen to accept the changes and import the workflow.
- Your workflow is imported and you are presented with a screen with additional configuration details. Click Done to exit this process.
All custom fields will have brand new custom fields created. This is regardless of a custom field of the same name / type already existing. See: JRA-37358 - Workflow import creates duplicate custom fields Open for the request to improve this.
Was this helpful?
Thanks for your feedback!