Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

how to move items between teammanaged projects without losing content

Ariane Cannenburg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 27, 2024

The team was split in two teams; we have to move from one project to the other (new) project. 

But looks like it doesn't keep the content of fields, it looses data...

 

 

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 27, 2024

Hi @Ariane Cannenburg -- Welcome to the Atlassian Community!

The issue type, field, and other configurations are distinct for each team-managed project.

A couple of possible workarounds for this scenario may be:

  • use export / import
    • export all issues with their fields for the source issues, including some uniquely identifying information (e.g., Summary);
    • move the issues to the new project;
    • export the new issues to get their key and unique identifying information;
    • use spreadsheet functions to combine the export data; and
    • import the fields to update them
  • use global context / shared fields
    • create global (i.e., company-managed) fields to be shared between the projects
    • update the projects to include the fields
    • for the source project, use an automation rule or export / import to move the data to the new fields
    • now when the issues move to the new project, the fields will likely be preserved

 

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events