nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Importing a project with attachments: Why ist Projectname expected instead of Projectkey?

Thilo Brause

We are currently merging two instances of jira and migrating project by project.

We have a project named "Alpha" with a Projectkey "ALP". We created that project on the new target instance, exported it on the old instance and copied avatars and attachments into position.

So the attachments lies now for example under .../application-data/jira/import/attachments/ALP/ALP-7

But the Importer expects them unter .../application-data/jira/import/attachments/ALPHA/ALPHA-7

Do we have to rename every folder and subfolder?

Or is there a way to configure that?

Accepted answers

Thilo Brause

We migrated our jira to a clean Installation on a new VM and now the described behaviour is no longer reproducible. Seems to be an Anomalie out of a serveral times upgraded jira-instance.

All comments

Ravi Varma

Hi @Thilo Brause,

Please note that JIRA Project Key is unique. So, when you try to merge two instances, you should be careful with the project keys on the target system.

If the project key already exists in the target system, then you should use another key.

Please note that the import related files should be placed as per the new project key.

In your case, all the files in /application-data/jira/import/attachments/ALP/ALP-7 should be placed under /application-data/jira/import/attachments/ALPHA/ALPHA-7 and it would be applicable for each issue in the project.

Yes, you have to rename ALP-/ALP-xxx to ALPHA/ALPHA-xxx.

To address this scenario, following is my recommendation:

Before initiating merge, rename the ALP project to ALPORIGINAL on target instance.
Once the project key is renamed, the ALP key will be available on target JIRA instance. This key can be used for importing the source ALP project to the target JIRA instance
The project import process will not complain now and will fetch the attachments from /application-data/jira/import/attachments/ALP/ALP-7

Hope this address your concern.

Regards,

Ravi Varma

Thilo Brause

Dear @Ravi Varma,

thanks for your fast answer. I just noticed I was unspecific in two points:

1.) We move only projects to the other instance that didn't exist there before

2.) We use the "Import Project"-Functionality of JIRA

So to import project ALPHA, with Key ALP in the new instance, I had to creat a new empty project with that key and name in the new instance as first step. And on importing the project at the point, the attachments were expected by the project-import-functionality to be in a folder-structure based on the project-name and not as you indicated, in folder-structure based on the project-key.

Ravi Varma

Hi @Thilo Brause,

Please note that projects are identified by project keys only.
If no source project exists in the target instance, then it should be straight forward.
Create the project in the target instance with same project key.
Copy the source folders to t arget folder /application-data/jira/import/attachments/ALP.
You should not face any issue, as project key ALPHA is not referenced anywhere and the project key in both source and target is ALP.
If you are still facing issues, then please share some screenshots from both source and target instance to understand the problem better. Also, share the JIRA version number of source and target instances

Regards,

Ravi Varma

Thilo Brause

We migrated our jira to a clean Installation on a new VM and now the described behaviour is no longer reproducible. Seems to be an Anomalie out of a serveral times upgraded jira-instance.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

import