How do the custom fields merge work?

Learn how Dr Pro for Jira merges custom fields, requiring AI for language recognition and duplication checks during migration.

✅ AI Requirement: Custom field merge needs AI enabled for accurate processing.
🌍 Language Recognition: Utilizes Google Translate for language understanding.
🔍 Duplication Check: Identifies duplicate fields across different languages.
🔄 Migration Process: Merges fields created during server-to-cloud migration.
🛠️ Advanced Mode: Users can select fields regardless of AI recommendations.
⚙️ Context Adjustment: New contexts are created for merged fields with different values.
🚀 Efficient Migration: Handles thousands of tickets and filters seamlessly.

🤖 AI Dependency: The merging process relies on advanced AI algorithms for language processing and duplication checks, ensuring data integrity across multiple languages.
📊 Data Migration Complexity: Fields migrated from older systems may have different values, necessitating careful context adjustments to maintain data relevance.
🔧 User Flexibility: By allowing users to merge any fields in advanced mode, the tool accommodates various user needs, enhancing customization capabilities.
⚖️ Context Importance: Properly setting contexts is crucial for effective merging, as different field types can lead to inconsistencies if not managed properly.
⏳ Time Consideration: Merging can take time depending on the volume of data, highlighting the importance of planning during migrations.
📑 Filter Management: Automatic updates to filters ensure that users do not have to manually adjust their settings post-migration, streamlining the process.
📐 Layout Adjustments: Users may need to manually adjust layouts after merging, indicating potential areas for future tool enhancements.