-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Import/Export - Site Export
-
7
-
Minor
Summary
Attachments of renamed projects get exported with the old project key in backup
Steps to Reproduce
- Create an issue in an existing project, e.g project key=ES
- Add an attachment to an issue
- Rename the project key, e.g set new project key to AA
- Generate an export file
- In the attachments folder, there will be no folder with the AA key. There will be a folder with the ES key
- Import the export file to a target instance
- The project will be created with the new key AA and the attachments will be linked to the correct issues
Expected Results
To have attachments folder exported with the updated project key
Actual Results
Attachments folder is created with the old project key
Notes
- Jira won't allow any new projects to be created or renamed to a project key which was already in use, i.e ES.
- Even though the backup XML file stores the project names in the original key in the attachment folder and if the cloud backup export was gathered after the project key change, then importing the same backup file to a site should work as expected and the attachments should be updated in the projects with the latest project key.