Issue Summary

When deploying configuration changes (specifically Jira Software workflows) from a Sandbox environment to Production, the deployment completes successfully. However, any subsequent deployment scan continues to detect the same workflows as "updated" or pending changes, even if no further modifications were made in either environment. This indicates a failure in the deployment comparison logic to correctly update the state/baseline after a successful sync.

Steps to Reproduce

1. Make changes to one or more workflows in the Sandbox environment.
2. Navigate to the Sandbox deployment tool and run a scan to detect changes.

1. Deploy the changes to the Production environment.

1. Confirm that the deployment log shows a successful status and that the changes are visible in Production.

1. Run a new deployment scan immediately after the successful deployment without making any new changes. Some workflows will be listed again.

Expected Results

The subsequent scan should show no pending changes for the workflows that were just deployed, as the Sandbox and Production states for those specific objects should now be in sync.

Actual Results

The deployment scan continues to flag the previously deployed workflows as "updated". They appear again as pending changes in the deployment UI, suggesting the comparison logic is stuck in a state where it perceives a difference that no longer exists or fails to acknowledge the new Production baseline.

Workaround

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