Articles
User Fields Don't Sync
User fields (assignee, reporter, watchers) don't sync due to Jira Cloud API privacy changes in Exalate Classic. Replace nodeHelper.getUserByUsername with nodeHelper.getUser(accountId) or getUserByEmail.
Can't Get Workflow Scheme for Project while Syncing Statuses
Problem You're syncing statuses with the Jira Cloud instance and you've got an error that mapping cannot be found. Error Details: javax.script.ScriptException: com.exalate.api.exception.IssueTrackerException:
Can not get workflow scheme ...
Error Creating or Updating Issue: Field Can't be Set
Resolve Exalate issue creation/update errors due to missing screen association. Ensure field on Create Issue and Edit Issue screens; check status edit permissions for add-on user.
REST Exception while Getting User by Username `null` on Jira Cloud
Fix REST exception "getting user by username null" (404) on Jira Cloud in Exalate Classic. Replace nodeHelper.getUserByUsername with replica.userField or nodeHelper.getUserByEmail for GDPR API changes.
Updating Comments or Worklog Doesn't Put Issue under Sync
Fix comments or worklog updates not triggering sync in Jira Cloud with Exalate Classic. Contact support@exalate.com to enable webhook processing on nodes.
Syncing Attachments Throws Maximum Filename Size Error
Resolve attachment sync failure with filename length exception in Exalate Classic to Jira Cloud. Shorten names before upload; error from MediaApiStreamAttachmentStore limits.
Custom Fields Don't Sync
Custom fields don't sync if missing from Issue View screen in Exalate Classic. Add field to Issue View screens for create/edit; no errors but values fail silently.
Subtask Sync between Team-Managed Projects Fails
Fix subtask sync failure between Jira team-managed projects in Exalate Classic. Use issue.typeName = "Subtask" (no hyphen); company-managed uses "Sub-task".
Exalate Can't Comment on the Jira Issue
Fix Exalate "no permission to comment" error in Jira workflow. Remove jira.permission.comment.group property from status; prevents add-on user commenting.
Attachment Sync Fails Because it Takes Too Long
Resolve Exalate attachment sync failures from session timeouts on Jira Cloud. Raise support request to support@exalate.com for node configuration increase.
"Project key is not set" when Syncing Issues via Local Connection
Fix "Project key is not set" error in local Exalate Classic sync. Select correct connection matching source issue's project in Sync panel; issue must belong to connection's projects.
Problem Filtering Internal Comments on Jira Service Management
Prevent Jira Service Management internal comments syncing externally in Exalate Classic. Use replica.comments = issue.comments.findAll { !it.internal } in Outgoing; requires request type set.
Known issue: Projects List isn't Available during Connection Setup
Fix projects list not loading during Exalate Classic connection setup (Jira Cloud to other apps). Clear browser cache or use Incognito after 3+ connections; rare caching issue.
Java.sql.SQLException: Incorrect String Value
Fix Java.sql.SQLException "Incorrect string value" for emojis in Jira Cloud MySQL with Exalate Classic. Add regex filter to strip emojis from description/comments in Outgoing sync.
Invalid Issue Type Selected
Fix "Invalid issue type selected" error from deleted next-gen project scopes in Jira Cloud with Exalate Classic. Permanently delete trashed projects or map issue types by ID in Incoming sync.
Connect Operation Does Not Sync Existing Comments, Attachments and Worklogs
Jira Cloud Connect button skips existing comments, attachments, worklogs. Use Bulk Connect issues from Exalate admin for full historical sync; unexalate first if needed in the Classic experience.
Impact on Exalate Functionality when Jira Site URL Changes
Changing Jira Cloud Site URL breaks Exalate app functionality. Revert URL or contact support@exalate.com if reverting not possible.