Project Configurator for Jira Server and DC

Support for Third-Party Applications

Conditions, Validators, and Post-functions

Project Configurator supports conditions, validators, and post-functions defined in standard Jira plus the following apps:

  • Jira Suite Utilities

  • Jira Workflow Toolbox

  • Jira Misc Workflow Extension

  • Jira ServiceRocket Utilities

  • ScriptRunner for Jira (Behaviours, Workflows, and canned scripts included with this app)

Data of any app that implements the extension points defined in Atlassian’s Extending the Jira Import Plugin page is supported. Also, any custom field values belonging to custom fields whose types are defined in an app will be imported if that custom field type implements the interface "com.atlassian.jira.imports.project.customfield.ProjectImportableCustomField".

Integration with ScriptRunner for Jira

ScriptRunner for Jira is a collection of powerful but easy-to-use workflow functions, JQL functions, listeners, and services, enabling the automation of a whole range of tasks in Jira and other tools in the Atlassian ecosystem.

The following integrations are supported in Project Configurator v. 3.2.0 and later. You must also have ScriptRunner for Jira version 6.0.2 or later installed on both your source and target instances to use Project Configurator to migrate ScriptRunner behaviours or workflows.

ScriptRunner Behaviours

Project Configurator handles the migration of ScriptRunner for Jira behaviours. Behaviours give you more control over fields in Jira. A field configuration customises how fields behave, based on the issue operation screen they appear on. However, a behaviour in ScriptRunner allows you to take that field customisation further, defining how fields behave for issues in a given project or issue context.

You can create behaviours to:

  • Make a field mandatory depending on other data entered on the issue screen.

  • Make a field read-only dependent on user role or group.

  • Conduct server-side validation of field data, before the issue screen is submitted.

  • Set a field value depending on other issue screen data.

When generating an export file, Project Configurator detects any behaviours you have configured related to the exported projects and includes them in the export file. To learn more about ScriptRunner behaviours, see our ScriptRunner documentation.

ScriptRunner Workflows

Project Configurator handles the migration of ScriptRunner for Jira workflows whether built-in or scripted. ScriptRunner for Jira Server uses scripted versions of workflow functions to extend and customise the automated tasks available in Jira workflows. These workflow functions include scripted validators, scripted conditions, and scripted post functions.

As with many features of ScriptRunner, you can select from built-in options, you can customise the built-in functions, or you can write your own.

These scripted workflow functions allow you to do a lot more with your Jira workflows and further enhance your automation. For each of the Jira workflow functions, ScriptRunner for Jira provides scripted versions, so that you can suit your workflows to your exact needs. There are three main types of scripted functions: script validator, script condition, and script post function.

When generating an export file, Project Configurator detects and correctly handles any ScriptRunner conditions, validators, or post functions in the exported workflows. When importing this file, these workflows are either created or updated in the target instance.

To learn more about ScriptRunner workflows, see our ScriptRunner documentation.

Only in-line scripts are handled by Project Configurator. If you are using script files rather than in-line scripts, you can manually promote the scripts according to the origin of the scripts.


  • Use your VCS to deploy appropriate scripts to the correct locations.

  • Install the same script plugins at both the source and target instances.

  • Manually copy the source scripts to the target.

Visualise the Migrations

ScriptRunner behaviours and workflows are handled in the Import Operations Tree like other calculated objects and changes.

You can use the Import Operations Tree features as follows:

  • Expand and collapse categories, individual objects, or concrete changes

  • View the separation of changes to new objects from changes to objects that already exist at the target instance

  • Enable or disable individual changes or groups of changes

  • Detect missing dependencies and requirements

  • Recalculate dependencies on demand

  • Text download of all the import information