[JIRAALIGN-1907] Features may not be updating the timestamps in the Jira Align database

Issue Summary

A customer with an instance connected to Jira Align Enterprise Insights (i.e. LEO) noticed that some Features were taking a long time to get their latest changes picked up by Enterprise Insights. In the user's case, they created a new acceptance criteria inside the feature, but, the changes were not reflected in Enterprise Insights until 12 hours later.

Steps to Reproduce

1. Jira Align instance connected to LEO
2. On Jira Align, add an Acceptance Criteria to a Feature.
3. Check Enterprise Insights for changes.

Expected Results

Enterprise Insights performs an incremental extraction throughout the day and will pick up any changes made to work items and reflect them accordingly.

Actual Results

Changes are not picked up in Enterprise Insights until 12 hours later, when it pulls the whole table as a catchup.

This was initially escalated to our Enterprise Insights Team and their findings are below:

We believe that this is in fact a Jira Align application defect.

Enterprise Insights performs an incremental extraction throughout the day. For Feature Acceptance Criteria (tblAgileAC_FeaturesEpics), it checks the CreatedDate and LastModifiedDate for timestamps for updates since its last execution. Overnight, it pulls the whole table as a catchup. What we believe is happening (we've seen this before on other objects) is that Jira Align is not updating the timestamps on the table and therefore EI doesn't pick up the record until the overnight full refresh. We would like to try marking this as a defect for the Jira Align team to resolve so that the timestamps are always maintained on create and modify.

Workaround

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