In some cases, importing custom field configurations with the "Smart custom field contexts" option enabled produces some inconvenient results:
- Sometimes it creates several custom field configuration schemes with the same name (even if they apply to different projects). This is confusing and it may produce problems if that configuration is migrated later without the smart custom field contexts option.
- In a few corner cases, the process followed and the results were not clearly defined.
- It did not adapt well to the new architecture of Project Configurator 3.X. Specially in some cases the information delivered to the users about the changes to be applied to the target Jira was quite unclear.
This change solves all these issues. It is designed to provide a set of clear guarantees about the final result, which are documented at this page. Please see there for further information and advice on how to use this feature.