Project Import responds with Required status error
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When importing a project you receive an error regarding a status being required even though it is present in the JIRA instance that you are importing into.
1
2
3
4
5
6
7
8
9
The status 'TO DO' is required for the import but does not exist in the current JIRA instance.
The status 'TO DO' is in use by an issue of type 'Sub-task' in the
backup file. The workflow 'YYZ: some Workflow', which is
associated with issue type 'Sub-task', does not use this status. You
must either edit the workflow to use the status or associate a workflow
with issue type 'Sub-task' that uses the status.
See the documentation for more informationDiagnosis
Cause
Note the capitalization of the status. In this particular example the source data had a status of 'TO DO' but the destination had a status of 'To Do'. Even though you chose to map the status it doesn't see the status as exact and will still throw the above mentioned error.
Workaround
Workarounds are ways to temporally circumvent a problem, although it still exists in the application.
Open the entities.xml from the backup you are trying to import from. You should find a line similar to the below near the end of the file. Edit the "TO DO" in this case to match the correct capitalization of the status in the destination instance and you should now be able to import the project without error.
1<Status id="10002" sequence="9" name="TO DO" iconurl="/images/icons/statuses/open.png" statuscategory="2"/>
Was this helpful?