The default scheme "System default field configuration" is not exported to XML, as it cannot be modified. Projects that use it will not have a "fieldConfigurationScheme" element in their XML description.
Locked custom fields are not exported
New since version 2.0.4-JX
Locked custom fields are not exported. This means that, when the configuration is imported, these custom fields will not be created or modified by Project Configurator at the target instance. This is consistent with the expectation that these custom fields are created/configured only by the plugin or application that created them (for example Jira Agile/Software).
See PCP-506 for other details.
An import may change the priority schemes of existing projects and, as a result, some of the issues in those projects might be left with priorities that are no longer allowed by the new scheme. If this is about to happen the simulated configuration import will show warning messages like these:
The first kind of message is issued when simulating a change to an existing priority scheme. It means that a total of 18 issues, possibly across several projects, have priority "Major" that will be left out of the new scheme configuration. The second message is issued when simulating association of a new priority scheme to an existing project. Likewise, it means 23 issues in that project have priority "Critical", that does not exist in the new scheme.
After applying the changes, those issues will be displayed with a "Not available" tag, next to their priority. It is up to the Jira administrator, either to bulk move them to another priority supported by the new scheme or to leave them like that.
Default priority scheme
If any of the projects using that workflow scheme has issues in a status which does not exist in the new workflow assigned to the issue by the draft scheme, this automatic migration will be impossible. In this case the user would have to map manually statuses in the old workflows to statuses in the workflows in the draft scheme. In this case, the import will continue and a warning will be shown in the load trace like this:
If a workflow scheme draft is left unpublished, either because the import option "Try to publish drafts" was not checked or because it requires status mapping by the user, a special reminder will be shown above the load trace. This reminder will tell the user that publishing the workflow scheme draft is a pending task. It wil include a link that opens (in a new browser window) the Jira page where the user can map required statuses and click to finish publishing the scheme draft.
If the import option "Try to publish drafts" is not selected, the draft will be left unpublished, but a reminder will be shown above the load trace telling that publishing the draft is a pending task. This reminder includes a link that will open (in a new browser window) the Jira page where the user can publish the draft workflow manually.
If the statuses and steps of the draft do not coincide with those of the original workflow, it is not possible to publish the draft (either automatically or manually). If this happens and the import option "Try to publish drafts" is enabled, the load trace will display a warning like this, including the error found in the draft:
Fixing this problem implies editing the draft until it is compatible with its original, or discarding it.
Workflow layouts are supported, starting with version 1.9-X of the plugin. Please be aware of these limitations:
| ||Source version|
|6.1, 6.2, 6.3||YES||YES||YES|
WARNING: Layouts may become unusable
and it would be impossible to edit them.
In this situation, consider skipping "Workflow layouts"
in the configuration import.
This happens with the default versions of the Jira Workflow Designer Plugin shipped with each version of Jira. It might be possible to fix these incompatibilities by upgrading one or both instances to the same version of the Jira Workflow Designer Plugin, but we have not tested that yet.
Jira users that click on the "View workflow" link (see next image) will also correctly see the new layout:
The plugin supports conditions, validators and post-functions defined in standard Jira plus the following plugins:
Workflow extensions defined in other plugins could not load correctly, if their XML descriptor (as obtained with Jira export workflow to XML function) references internal IDs of entities like custom fields, groups, roles, etc. and those IDs are different in the origin and target instances. The recommended workaround in these cases is either:
If you need Project Configurator to handle workflow extensions defined by a plugin, please raise an issue here.
Additionally, a special reminder will be shown above the load trace, telling the user that assigning manually the new workflow scheme to the project is a pending task. This reminder includes a link that will open (in a new browser window) the Jira page where the user can map required statuses and click to finish assigning the new scheme.
The usual strategy of halting the export with an error message if a missing reference is found, is not always convenient with gadgets in dashboards. Many dashboards have been created by normal Jira users and it would be too much of a burden on the Jira admin having to fix references in all of these before being able to export dashboards successfully (see discussion starting at this comment). The solution since v1.5.1 is the following:
As of version 2.1.4:
If you try to export a project with an old version of Jira Agile, you will get the warning from the image below.
If you try to import a project with an old version of Jira Agile, in the import trace, you will get the warning from the image below.
If importing complete projects (i.e. their configuration, issue data and attachments) links between issues that existed in the source instance will be recreated in the target instance, as long as projects for both linked issues are imported. If only one of the projects is being imported into the target, the issue link will not be created. However, if the other project is imported later, then the issue link will be created at the moment of this second import.