Keep all values when migrating issues

Jagmohan
Contributor
August 16, 2023

Hi all,

 

When I want to migrate an issue between two software projects, many values are deleted. There is no way to map these fields in the "Move issue" wizard.

 

We work with sprints in project 1 while the other project is kanban. I've created the same fields in the kanban project which are in the sprint project (see image)

Screenshot 2023-08-16 at 15.17.04.png

But when I'm moving the issue, the values are not mapped.

Screenshot 2023-08-16 at 15.17.57.png

Where do I map these fields between projects?

 

Curious to know

1 answer

0 votes
Kian Stack Mumo Systems
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 16, 2023

@Jagmohan

 

Is there any context set on these custom fields limiting them to a specific project and.or issue types?

 

Thanks,

 

Kian

Jagmohan
Contributor
August 20, 2023

Hi @Kian Stack Mumo Systems

The custom fields I want to migrate were created in the first project (sprint structure). Then we created a second project (kanban style). When moving stories, these fields would lose the values because there were no fields to map to in the kanban project. I could not select the sprint project custom fields in the kanban project.

So I created new fields identical to the ones in the sprint project, but there is no way to map them. As far as I know, they are not limited to a project as I can select the new fields in the sprint project as well. Also: the newly created fields are available in the Custom Fields screen, but not the old sprint project related fields.

See images below

Screenshot 2023-08-21 at 08.23.59.png

Screenshot 2023-08-21 at 08.19.20.png

Screenshot 2023-08-21 at 08.11.35.png

 

Hope this provides more context and thanks for your help <3

Kian Stack Mumo Systems
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 21, 2023

@Jagmohan

 

Yes, this does.

 

The issue is that you are trying to move issues from a Team Managed project to a company managed project.

 

Team managed custom fields are completely unique from the custom fields you've created for your Kanban project. As such the values won't transfer. 

 

Please review this documentation for information on migrating team managed -> company managed.

Like Jagmohan likes this
Jagmohan
Contributor
August 24, 2023

Thanks for the reference documentation @Kian Stack Mumo Systems - that explains a lot. Now the next step (:

I read the following:

Custom fields: If you use custom fields in your team-managed project, a Jira admin needs to recreate the fields and add them to screen schemes and field configurations in your company-managed project. Custom field data will need to be recreated, otherwise it will be lost.

Okay: the fields have been created and added to the screens. I don't understand what is meant by "Custom field data will need to be recreated" or how to do it. 

Back to my original question: is it possible to map those fields between team-managed > company-managed projects?

Kian Stack Mumo Systems
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 24, 2023

No. You would need to export your issues from your Team managed project first. Then move the tickets to the new project, and then reimport those values using a csv import.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events