Project Import fails with "issue type scheme" error

Error message:
"The issue type 'Feature' exists in the system but is not valid for the projects issue type scheme"

But the docs on importing projects at https://confluence.atlassian.com/display/JIRA052/Restoring+a+Project+from+Backup say:
"Issue type screen schemes — Not applicable. Issue type screen schemes do not need to match between the backup and target instance of JIRA."

Is that a contradiction or do I interpret the documentation wrong?

How can I best make that project import work, since the "default" issue type scheme is not editable and there is no setting for selecting a different issue type scheme on import?

2 answers

1 accepted

Dear David,

The issue type 'Feature' exists in the system but is not valid for the projects issue type scheme

As for the above error which was produced when importing a project, this indicates that the issue type scheme mapped to the project do not include the issue type "Feature", which is mapped to some of the issues in the project. So basically this should concern the Issue Type Scheme configuration, and can be fixed by including the "Feature" issue type in the related Issue Type Scheme.

But the Issue Type Screen Scheme should be different than the Issue Type Scheme. Basically we use the Issue Type Scheme to map certain issue types to a specific project, and the issue type screen scheme is to map specific screen to issue operations for a specific issue type. Hence, the Issue Type Scheme preparation is mandatory, while the Issue Type Screen Scheme is not applicable when importing a project.

I believe that this details is included in the following documentation:
- https://confluence.atlassian.com/display/JIRA052/Restoring+a+Project+from+Backup#RestoringaProjectfromBackup-PreparingyourtargetJIRAinstance

  • If an issue type has been used in your backup project (i.e. there are issues of this issue type), you must set up the same issue type in your target JIRA project. You may want to consider setting up Issue Types for the project instead of globally.

I hope that this helps!

Thanks.

Thanks, Ahmad,
that fixed the issue.

The original project was imported from an external system (Fogbugz). After exporting, deleting the project, and re-importing it from the backup file using the Default Issue Type Scheme I hit that error.
Setting up a new project of the same name before import, copying the Default Issue Type Scheme and adding the "Feature" issue type to that scheme, then using it in the new project made the following project import work.

Great to know that the issue is now fixed on your end David.

Have a pleasant day!

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Marketplace Apps

Tips on how to choose the best estimation method for your planning

Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...

65 views 0 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you