Details
-
Suggestion
-
Resolution: Unresolved
-
1
-
10
-
Description
Summary:
Custom field configuration is not retained when being migrated from Company managed projects to Team managed projects.
Based on the following documentation Migrate between team-managed and company-managed projects
Custom fields
To migrate, you need to recreate your custom fields in your new team-managed project. Team-managed project fields are independent of global custom fields. When you move requests to a team-managed project, Jira retains most of your request's global custom field values (except the component and version fields). However, these are not mapped to your team-managed project's fields.
Your global custom field data is stored against your requests but the fields in your company-managed project are technically different from the fields in your team-managed destination, so when migrated they will appear blank. The data is recoverable if you move the issues back to the company-managed projects they came from.
Suggestion:
Ability to retain customer field value when being migrated to team managed projects.
Attachments
Issue Links
- is cloned from
-
JSWCLOUD-20980 Option to retain a value when moving an issue from a company-managed project to team-managed
- Closed
- was cloned as
-
JRACLOUD-79147 Option to retain a value when moving an issue from a team-managed to company-managed project
- Gathering Interest