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

Moving ticket from one project to another the field values are not retaining

Savita Praveen

Scenario:

I am trying to move customer tickets from one project to another project for engineering. The issue type has specific field values captured for the ticket. Now I am moving it to another project and issue type which has matching field configuration.

Problem: Though I am checking the retain checkbox in the issue migration screen the values are not retained for some fields.

Can someone help me here?

-Savita

Accepted answers

M Amine

Are you in a company-managed or team-managed projet?

In order to retain values, you need to have the same fields in both issue types. Meaning:

If you have a text field named "A" mapped to source issue type and projet, the same text field should be available for the destination issue type and project
Same rule applies for other custom field types

Do you have that?

All comments

M Amine

Are you in a company-managed or team-managed projet?

In order to retain values, you need to have the same fields in both issue types. Meaning:

If you have a text field named "A" mapped to source issue type and projet, the same text field should be available for the destination issue type and project
Same rule applies for other custom field types

Do you have that?

Savita Praveen

Hi @M Amine

Both the source and destination projects are team-managed projects and i create same replica of fields and values in both project issue type but still the values are not retaining.

Only change I see is-

1. Source issue type is bug/task and destination issue type is Customer support.

2. Workflow for those issues types are different in both the projects.

Would that be a problem here?

-Savita

M Amine

Hi @Savita Praveen

I'm afraid it won't work because custom fields in both team-managed projects are not really the same. They may have the same "name" but the custom field id is not the same and hence there are not the same. The method I described will work only of company managed projects. Here is a link explaining this.

Your global custom field data is stored against your requests but the fields in your company-managed project are technically different from the fields in your team-managed destination, so when migrated they will appear blank. The data is recoverable if you move the issues back to the company-managed projects they came from.

Savita Praveen

Got it. As we have team-managed-project this might not help much. Anyways thanks for the information. Appreciate that.

-Savita

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud