Sharing your workflow

The workflow sharing feature lets 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 way, you can easily share and use workflows others have published. You can also move a workflow from staging to production in your organization.

On this page:

Exporting your workflow

If you'd like to share your JIRA Workflow with another JIRA instance or upload it to the Atlassian Marketplace, first download it as a .jwb (JIRA Workflow Bundle) file. Here's how to proceed:

  1. Choose > Issues.
  2. Find the workflow you wish to share by clicking on the Workflows section in the left-hand panel.
  3. Click View or Edit under the Operations column.
  4. Select Export > As Workflow. You will see this screen:

    Export Workflow screen
  5. Click Next to continue.
  6. 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).
  7. 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. Another good resource is Step-by-step Paid-via-Atlassian Listing.

  1. Create an account on Atlassian Marketplace.
  2. Log in to the Atlassian Marketplace. 
  3. Click Manage listings from the site header. 
  4. Click Create add-on.
  5. Fill out fields accordingly. 
    A few notes as you complete your submission:
    1. List your add-on as Public unless your workflow contains sensitive information. Private workflows can't be uploaded to JIRA Cloud.
    2. Upload or link to your .jwb bundle.
      Choose either Upload your add-on artifact or Provide a URL to your artifact:
      Choose the appropriate option
    3. The Summary field contains the information users see when searching the Marketplace.
    4. The Category for your workflow must be Workflow Bundles. 
      Choosing Workflow Bundles ensures other JIRA users will have visibility to your workflow.
    5. The Add-on key must be unique.
      This is something that uniquely identifies your product; it will become the product URL.

Once you accept The Atlassian Marketplace Publisher Agreement, the system submits your add-on for review by Atlassian's Marketplace  team.

Importing from Atlassian Marketplace

This procedure covers importing a workflow from Atlassian Marketplace.

  1. Choose > Issues.
  2. Click on the Workflows section in the left-hand panel.
  3. Click Import from Marketplace.
    Import from Marketplace
    You'll see this screen:
    Select a workflow
    This screen displays the available workflows, ordered by popularity (determined by the number of downloads).
  4. Find the workflow you want and click the Select button.
  5. 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. For importing from Marketplace, see the procedure above, Importing from Atlassian Marketplace.

  1. Choose > Issues.
  2. Click on the Workflows section in the left-hand panel.
  3. Select Import > Import Workflow.

    Import Workflow option
  4. Select a workflow from your computer to upload and then click Next.
  5. JIRA automatically generates a workflow name, but you can change this if you like. Click Next.
  6. 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.

    Map Worfklow Statuses screen

  7. You will be presented with a screen that presents a summary of the workflow changes, as shown below. Click Import at the bottom of this screen to accept these changes and import the workflow.

    Preview of import screen
  8. Your workflow is imported and you are presented with a screen with additional configuration details. Click Done to exit this process.
    (info) 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.

Custom fields in workflow imports

If the workflow that you are importing 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.

  1. 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:

    Custom Field Types & Searchers window

  2. Click to expand the list of enabled modules.
  3. 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.

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