Import conflict detection

Owned by Rosen Marinkov
Last updated: May 21, 2024 by Stanley Neychev
3 min read

On this page:

Import Conflict Detection is a reporting tool implemented in Project Configurator v2.2.0. If you are using Project Configurator v3.0.0 or higher, you should use the import simulation tool instead.

Locate any conflicts

The Import Conflict Detection report shows, for a given import file, the objects in Jira that would be mapped during the import as counterparts of objects included in the new configuration.

All mapped objects are shown, even if the new configuration does not imply changes to those objects. You can then use the results to help you assess any changes that are required before running an actual import.

Usually, when an object is mapped as the equivalent of another object coming with the import, it is because both of them have the same name. If this mapping produces undesired effects, it is considered a "name conflict".

It is important to note:

  • The objects in the report will be updated with the new configuration as defined in the file to be imported. This means their previous configuration will be overwritten (with some exceptions). In addition to the projects being imported, this might have an impact on other projects at the destination instance.

  • If the object included in the imported file and its counterpart at the destination represent different things, even if they have the same name, the result of the migration will be confusing for users. For example, what would the meaning of an issue with a Reopened status be after a migration if, at the destination instance, Reopened meant "rejected by the end user", but at the source instance, it meant "did not pass QA"?

Run the report

  1. In your target Jira instance, select Manage Apps from the Jira Administration menu, then select Import Conflict Detection under Project Configurator in the left sidebar of your Jira Administration screen.

    The Manage Apps screen, in the Administration window. The Import Conflict Detection option is highlighted in the left sidebar.

  2. Select the type of project import file you want to analyze using the Project File Type drop-down list.

    • select an XML configuration file to upload ("configuration only."); or

    • write the name of a valid zip file located in the {JIRA_HOME}/import/projectconfigurator folder ("complete project.")

  3. If required, you can skip one or more object types from the analysis by selecting them from the Skip drop-down list. Skipped objects are not included in the report.

  4. Click the Import Conflict Detection button to launch the report.

Report results

A progress bar is displayed while the report is running. On completion, a results page is displayed.

The left column of the report lists the objects that will be mapped as targets of objects included in the import file. The right column displays links to details of how objects are being used, where applicable. This follows the same rules and limitations as the object dependencies report that you run on your source instance.

Click a corresponding link to see where the object is used. In the example below, Priority Highest is used in the Default Priority Scheme and Project Demo Priority Scheme.

The Potential Import Conflicts section of the Manage Apps tab.

Using the results

If you want to make changes to your migration setup before running an actual import, you can use the results to identify which object or projects you want to modify. You may want to make changes to your source instance or change your export options and create a new export file, or you may want to change your import options; for example, you may want to skip objects.