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

Migrated issues from one project to another project is not showing linked fields details

Kay_8f3uo0

I migrated issues from a team-managed project to another team-managed project but the information of the linked jira field in the first project is not displaying in the second project when I click on an issue after migration.

Do I have to create another custom field for the new project or how can I resolve this?

Accepted answers

All comments

Trudy P Claspill

Hello @Kay

What is the "linked jira field"? Can you show us an example of an issue in the source project with that field and an example of that field in a migrated issue in the destination project?

Kay_8f3uo0

I do not have a screenshot of the issue in the source project as I have migrated all to the new project but I have a attached a screenshot of the issue in the new project.

All the jira field in the previous project were populated but it is not showing in the new project. All the issues migrated were done/resolved issues and their jira fields(linked field) were showing in the previous project but not in the new project.

I transitioned an issue back to the source project to get a screenshot of the jira fields but it did not show again even in the source project

Trudy P Claspill

Hello @Kay

Some fields are system defined and will be able to receive the data when issues are migrated between projects, like the Summary and Description fields.

Some system defined fields are list fields, like Issue Type and Status, and the ability to receive the data depends on whether or not the list has the same values.

In Team Managed projects it is also possible to reuse Globally defined custom fields (fields that have been set up for Company Managed projects). In that case if the two Team Managed projects reused the same Global custom field, then the data should transfer successfully during the move of an issue.

However, Team Managed projects support creating custom fields that are local to just the one project. When that occurs the data will not move successfully from one project to another, even if both projects have a field with the same name and configuration. Custom fields that are local to the team managed project are unknown to other team managed projects. When you move an issue from one project to another, Jira has no way to determine the destination field for those locally defined fields. The data is deleted during the issue moving process. It won't be recovered is you move the issue back to the original project.

Kay_8f3uo0

The custom field are global custom field, see example of config. shot Screenshot 2024-03-11 at 8.58.35 AM.png

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-service-management-cloud

jira-service-management