Project Configurator issue

[Roy Chapman]

Trying to import a project configuration, reports

Issue Type

The sub-task issue type 'QA Execution ' is required for the import but does not exist in the current JIRA instance.

The sub-task issue type 'QA Preparation ' is required for the import but does not exist in the current JIRA instance.

Both of these sub task do exist in the current JIRA instance.  How come they are not recognised?

QA Execution QA Script Execution	Sub-Task	Default Issue Type Scheme Banker Portal Documents Scheme BP Default Issue Type Scheme	Edit   Delete    Translate
QA Preparation QA Preparation and Update of Scripts	Sub-Task	Default Issue Type Scheme Banker Portal Documents Scheme BP Default Issue Type Scheme	Edit   Delete    Translate

[José Marañón [Awnaba Software S.L.] · Accepted solution]

I assume you found that error when importing project data with JIRA Project Import Tool.

By the reporting message, it seems as if the name it is looking for has a trailing whitespace, see the gap before the closing single quote and after the name of the subtask issue type: sub-task issue type 'QA Execution '. Probably the subtask types that exist do not have the trailing space.

Could you check if in the original instance the name had a trailing space?

[Roy Chapman]

How sneaky! This was the problem, both issue types on the source system had a trailing space. I have removed and can now export/import. Would the tool be able to trim trailling spaces from these fields?

[Roy Chapman]

How sneaky!  This was the problem, both issue types on the source system had a trailing space.  I have removed and can now export/import.

Would the tool be able to trim trailling spaces from these fields?