ArticlesPSA: Duplicate Project Tasks Created During Bulk Jira Sync Operations

• Duplicate Project Tasks are created instantly during bulk Jira sync operations
• Duplicate records share the same parent project, name and pse__Jira_Correlation_ID__c
• Issue does not occur during individual (non-bulk) pushes
• Issue persists after SP9 and SP10 deployments

PSA Direct for Jira

Two related bugs identified:

PSAJ-6932 (partially fixed in SP9): The parent link field was replaced by parent in cloud systems. The connector was searching for a parent task instead of the project, causing it to mishandle Epic-level syncs during bulk operations.

PSAJ-6958 (permanent fix in Summer 2026 release): Write-back correlation failure in fferpcore.TransformMappingService. When PSA creates a Jira issue in bulk, the returned Jira key is not reliably bound back to the originating task. The correct key is left orphaned; when Jira echoes the create back inbound, the connector finds no match (Rows:0) and inserts a new duplicate task.

• Duplicate rule workaround has a small risk: if Jira automation modifies mapped data during the initial sync, those changes may be lost on re-sync
• Permanent fix (PSAJ-6958) requires new metadata — cannot be delivered via a service pack
• Related case: 00496889 — Sync with Jira not initiating on project update (separate issue)