How to move issues without losing custom fields information

[SabrinaB]

Hi everyone,

I have a problem and I do not know the solution. When I move an issue from Project A to Project B, I lose information of the customs fields of Project A. Do you know a way to translate those custom information to "description" field or as a comment in Project B?

Many thanks for the help,

Sabrina

[Nic Brough -Adaptavist- · Accepted solution]

If you make the custom fields available in both projects, the data will be retained when you move the issues.

[SabrinaB]

Hi Nic,

thanks for the quick answer! The complexity of my problem is that I don't have those customs fields in the Project B. And I do not want them in this project. Do you know the way to transfert custom fields info into Comment or Description field?

Thanks for the help,

Sabrina

[Nic Brough -Adaptavist-]

Plenty of options, but they're all script/code/manual processes.

If I were you, I would add the fields to project B, but only put them on the "view" screen. That way, you'll keep your data, but no-one will be able to add/update them.

[SabrinaB]

Hi Nic,

The option of putting those fields only in the view screen is pretty good. Many thanks for the help!

Sabrina

[Nic Brough -Adaptavist-]

I should also have said, it's a good solution to get over the initial problem, then you can consider updates later if you really need them moved into other fields. And having them already on the issues makes the moving of the data a lot easier!

[Dieter]

I did not check it by myself yet but there seems to be a post function in this plugin https://plugins.atlassian.com/plugin/details/29496

[SabrinaB]

Hi Dieter,

many thanks, I think this plugin would be very useful for this problem and for other issues that I have with the workflow.

Regards,

Sabrina