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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.