Issue Summary

When using the Mass Move / Mass Update function in the Features grid to change the primary Program of integrated Features that share the same Program Increment (PI), the Jira Connector detects a mismatch between the new Program mapping and the existing Jira Space.

This causes the connector to unlink the associated Jira Epic (Jira issue(s) no longer associated to this feature) and clear the External ID from the Feature. Subsequently, selecting a new Jira Space on the unlinked Feature triggers a creation push, resulting in duplicate Epics in Jira.

Steps to Reproduce

1. In Jira Align, ensure Jira Connector is configured with two Jira projects mapped to two different Programs (e.g., Project A -> Program A; Project B -> Program B), both sharing the same Program Increment (PI).

1. Create an Epic in Jira Project A and allow Jira Connector to synchronize it as Feature A in Program A.

1. In Jira Align, navigate to the Features grid.

1. Use More Actions > Mass Move (or Mass Update) to move Feature A from Program A to Program B.

1. Allow the Jira Connector sync cycle to run.

1. Open Feature A in Jira Align and inspect the sync state / audit log.

Expected Results

The Jira Connector should either prevent changing the Program of integrated work items via Mass Move, or automatically validate and maintain proper synchronization mappings without severing the link to the existing Jira issue.

Actual Results

The Jira Connector unlinks the Jira Epic from the Feature, recording Jira issue(s) no longer associated to this feature in the Audit Log and clearing the external link.

If a user subsequently selects the new Jira Space in the Feature slide-out and saves, Jira Align treats the Feature as a new work item and creates a duplicate Epic in Jira.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available