Issue Summary

When a Feature is updated from Jira with an Accepted Date, the sync to Jira Align will pull both the state change to Accepted and the Accepted Date.

However, Jira Align will set the Accepted Date to the date of the Accepted State change in Jira Align instead of using the Accepted Date provided by Jira Sync.

Steps to Reproduce

1. Create a Jira Epic with the status "In Progress" and let it sync to Jira Align
2. Update the Jira Epic status to "Done" and update the Jira Accepted Date to yesterday
3. Let the update sync to Jira Align, and see the correct status of "Done" but the incorrect Accepted Date of today

Expected Results

The accepted date being pushed from Jira will be reflected in Jira Align on the initial sync

Actual Results

Jira Align updates the Accepted Date to the date of the Accepted state change, even if the Accepted Date was pushed along with the state change.

A second sync is required in order to have Jira push the correct Accepted Date.

This kind of action can trigger incorrectly the Jira Why field sync also.

Workaround

Currently, there is no known workaround for this behavior.

However, a second sync from Jira to Jira Align will correctly update the Accepted Date.

Features do not respect Accepted Date push from Jira when the Accepted state change happens in Jira Align