Jira Align synchronization failures due to certificate chain mismatches

Jira Align requires valid SSL/TLS certificates for secure communication with on-premise Jira instances. When utilizing self-signed certificates or those with incomplete CA chaining, the integration layer often reports generic connection errors within the Sync Status dashboard without granular TLS handshake details.

This issue is exacerbated when the Jira Align cloud service fails to resolve the FQDN of instances behind restrictive firewalls or proxies. There is documented uncertainty regarding how the system handles transient DNS timeouts during high-load cycles, often necessitating manual retries of specific sync jobs.

How can administrators access the specific TLS handshake error codes within the Jira Align integration logs? Is there a configuration-based method to import custom root certificates directly into the Jira Align environment to resolve validation errors?