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; } } }

When moving a ticket, the user-created context fields are not moved. Why?

Steffen_xj0qfh

I need to move issues from a Business project to a Software project. Each time I try, only the content from the standard fields are transferred. The content of the user created context fields are empty. However, as the user created context fields are filled with important information, I cannot ignore them. We are talking about approx. 500 tickets that need to be moved. My project role is admin and these are teammanaged projects. Access is private. I have also added the same issue types and context fields to the target project.

Accepted answers

Mark Segall

Hi @Steffen and welcome to the community!

Team Managed projects are very isolated. Even though you may have the exact same field names, behind the scenes they're seen as unique (they will even have unique custom field IDs).

Your best bet is to export the issues to csv and then perform an import to the new project. This will allow you to "remap" those fields to the appropriate fields on the new project.

All comments

Mark Segall

Hi @Steffen and welcome to the community!

Team Managed projects are very isolated. Even though you may have the exact same field names, behind the scenes they're seen as unique (they will even have unique custom field IDs).

Your best bet is to export the issues to csv and then perform an import to the new project. This will allow you to "remap" those fields to the appropriate fields on the new project.

Steffen_xj0qfh

Hi @Mark Segall, thanks for your welcome and the quick response. I already had the idea with the export. But I noticed that the comments are not exported. However, these are also very important. Is there a solution for this or am I doing something wrong here?

Mark Segall

Ahh comments... Yes you could take this approach:

Export all of the issues to csv so you have what you need for the custom fields
Move the issues to the new project so you can retain comments

Jira stores the old key value for reference so you may be able to perform an import of the custom fields you captured in step 1 against the original key. However, if Jira doesn't like that you would then:

Export all of the issues again to get the new keys
Perform a mapping in Excel of new key to old key (Jira does not move issues in any particular order so you would need to perform a vlookup)
Import the custom fields against the new key

Steffen_xj0qfh

thanks, I will try this.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud