Moving custom fields from Team managed to Company managed project

[Gayathri B]

Hi All,

I am right now having 3 custom fields created in the Team managed project, for which I have created 3 custom fields under the company managed projects global field list. 

When I move an issue from the team managed project that has values in the 3 custom fields, I do not have the facility to map those fields to the respective fields in the destination project - as we do for the statuses

What should I do to enable this? Otherwise it will be painful to manually update 2k+ issues this way :( 

Please help on the same. TIA.

Regards,

Gayathri

[Jack Brickey]

I hate to be the bearer of bad news but you will be unable to move custom fields from TMP to CMP Projects. Unless something has changed since I last looked.

[Gayathri B]

That is very unfortunate :( I will then have to take the data into an excel and then update it manually on all tickets. 

Is there a way to import only couple of columns from the jira of the source board to be imported into the target board? In that case I will have to define which fields should be mapped to which one.

TIA.

[Jack Brickey]

Sure. After creating the issues then use the following column structure in the CSV.

NewKey l CF1  l CF2 l CF3

the challenge will be ensuring you have a mapping from old key to new key so that the proper CF values are aligned to the new key.

be sure to test a single entry to ensure you have it right then proceed with rest.

[Gayathri B]

Thanks @Jack Brickey  for the response. But I dont completely understand what this means. 
What is NewKey and what are CF1, CF2 and CF3 ?

I will tell you the use case.

In the source board "PD", I have fields Due date and Release date

In the destination board "XY", I have fields Dev due date and Prod Release date

Once I move all the tickets from PD to XY, I will have to create a csv.

Now how should I frame the columns?

[Jack Brickey]

NewKey means the issue key associated with the issue after it is moved. CF1 = custom field 1…

so let’s say you have the following…

Current TMP project with project key = ABC, and custom field ABC_CF1

New CMP project with project key = XYZ, and custom field XYZ_CF1

For illustration purposes let’s say you have only 3 issues in your project: ABC-1, ABC-2, ABC-3 with a custom field values of: 111, 222, 333 respectively. Then the CSV would look like this…

NewKey    XYZ_CF1

XYZ-1        111

XYZ-2       222

XYZ-3       333

hope this makes sense.

[Gayathri B]

Yes @Jack Brickey that makes sense!

So now that the csv is ready with the newkey and the "to be updated values", is it safe to assume that the custom field name in the csv should be like this ?

Projectkey_customfieldname - ?

And once the csv is updated, which option should I use under the project in order to import or update the desired fields?

[Jack Brickey]

Sorry I am not following you on the custom Field name in the CSV - Projectkey_customfieldname.

basically you need to figure out how you can create that CSV file. The headers on the columns can be anything you want them to be the key is mapping those headings to the proper fields in the new project when doing the import. I suggest simply trying a test CSV file to get an understanding of how it will work. If the issue key of the new project is included for each row then all other fields that are mapped in the import will result in updating those specific issues.

[Jamie Schwartz]

@Jack Brickey What's the trick for matching the old keys to the new keys after the move? I see the Issue Id field when you export the data before the move seems to stay the same so are you saying we have to do a vlookup in excel to find the new key matched on the Issue ID then use that Issue Key field in the External System Import csv to ensure the freshly moved issues are updated? I was hoping since Jira is smart enough to redirect URLs that it would be smart enough to use the Issue ID or the old issue key as the key for updates instead of this extensive workaround.

SMH Atlassian on pushing out Team projects but making it a nightmare to move things around. 

[Andreas Lärkfeldt]

Workaround Deluxe for DATE fields!

If you as we wanted to move Resolution Date from Team to Company managed Project here is a workaround :D

1 - Resolution date is non existing in Team managed projects

2 - Therefor we need to add this manually (or with Automation and Bulk of course)

3 - Custom fields are not following between Team and Company managed projects on MOVE.

4 - Therefor you will need to reuse another field which is not "custom". In our case we use the field Due date :D

5. We copy the value we want to the field Due Date (which is a default value)

6. We move the issue to the company managed project

7. TADA - the value is listed in the field Due Date :D

From there on you're allowed to do whatever you want with it :)

Hope it helps anyone ...

And maybe you could reuse other default fields for text or similar ... haven't tried it :P

Kind regards

[Marlene Kegel - codefortynine]

Hi,

I'm Marlene from codefortynine. 

Another option would be to bulk clone and move the issues with Deep Clone for Jira.

It's possible to clone issues and custom field values between team managed and company managed projects, when the name of the field corresponds.

(There are some exceptions that can be found in our documentation.)

Navigate to

• Apps > Deep Clone > Bulk Clone
• Select all issues you want to clone as "source project", "source filter", or "source board"
• Select the project you want to clone the issues into as "Target project"
• Fetch issues
• Configure and bulk clone

[Deleted user]

Hi Marlene

Thank you for this - the Deep Clone tool works well however even when naming the custom fields identically the values within each field in the Team Project is not cloned to the Company Project... are you able to help?

[Marlene Kegel - codefortynine]

Hi @[deleted],

I am sorry to hear that cloning custom fields hasn't worked for you.

I've seen that you already contacted our support team. Thank you for getting in touch with us about that.