Lost data when migrating an issue between projects

Question

Hello

I'm guessing the answer to this question is 'no' but just in case...

Is there a way to restore data in a field that's been lost when migrating a Story from one project to another, because the field doesn't exist in the new project?

Many thanks!

Max Foerster - K15t · Accepted Answer

Hey @Maxine Freedman-Thompson

Can you give us some more information about what kind of projects you were moving the issues? Because the answer is it depends. There are a few things to keep in mind, and it heavily depends on the type of projects we're discussing. Did you move from a team-managed project to a company-managed project or vice versa?

There's a good article in the documentation that sheds some light on the topic: Migrate between team-managed and company-managed projects.

Coming from a company-managed project, most of the issue fields, except for components and versions, are retained but you will have to recreate the fields in the project or add them. The data will be back if you move the issues back to the original project.

Coming from a team-managed project, you will need to recreate the data in the fields. If you haven't done that, it's lost it's lost in the process but still accessible in the history.

Best, Max

ELFAPP Technologies · Accepted Answer

Hi,

The data would most probably exist in history (If they don't exist there then this method won't work). What you can do is export the issue data that contains this historical content. You can use this article which suggests via API. Edit the data to suit what you need for that field then use the CSV importer to import the value into the custom field for those issue keys. Make sure the field exists on the project and its value or options have already been configured.