Issue Summary

When the state is set to "Closed" at the Epic level in ADO and synced to JA, Accepted Date value is not updated and set as Null, JA API output for the Epic shows "acceptedDate" is also set to null.

 
"acceptedDate": null,

Additionally, the Accepted Date value in Enterprise Insight is reported as "Null."

Note:

• This issue does not occur at the Feature level.

• When any fields in JA are updated, AcceptedDate value is updated. 

  Steps to Reproduce

1. Step 1. Ensure that ADO and JA are properly mapped in Admin > Connector: Azure DevOps Settings. Map the project in the Projects tab, enable Epic on the Item tab, and map the state.
2. Step 2. In ADO, create an Epic and set the state to "Closed," then allow it to sync to JA.
3. Step 3. In JA, verify that the state has been updated to "Closed/Accepted."
4. Step 4. Checked the API output for the Epic and confirmed that "acceptedDate" is also set to null.

Expected Results

The Accepted Date field should be updated appropriately based on the Epic state.

Actual Results

The Accepted Date field is not updated and remains set to "Null."

Note: 

For Enterprise Insight (EI) users, when the epic is updated on the Jira Align side (for example, when the customer updates the description or other fields), the "Accepted" date field is updated in the EI epic-related table, and the "AcceptedDate" field is also updated in the API. However, this change was not captured in the audit log, which only shows the initial state change to "Accepted." in the audit log. 

Workaround

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