-
Suggestion
-
Resolution: Won't Do
-
1
-
11
-
Atlassian Update
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Joe Nguyen
jnguyen2@atlassian.com
Product Manager, Jira Cloud
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.
- 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
- mentioned in
-
Page Loading...