qTest-Jira Custom Field Mapping Performance Limits

Custom Field Synchronization Overhead

The qTest-Jira integration allows for bidirectional synchronization of custom fields to maintain consistency across the ALM lifecycle. While this ensures data alignment between requirements and test execution, there is a known trade-off regarding the volume of mapped fields.

In environments with extensive custom field configurations, the synchronization process may encounter performance degradation during large-scale data updates. It is unclear at what specific threshold the number of mapped fields begins to negatively impact the synchronization latency or the responsiveness of the Jira integration panel.

Technical Constraints

• Bidirectional sync frequency settings.
• Volume of custom field mappings per project.
• Data consistency requirements across platforms.

What are the recommended limits for custom field mappings to prevent performance degradation? Is there a documented maximum number of fields that can be synced before synchronization latency becomes critical?