Search before asking
What happened
After performing a full synchronization of Jira data, we found an issue that does not exist in the raw and tool layer tables. However, this issue is still present in the issues and board_issues tables in the domain layer.
What do you expect to happen
The issue should not exist in the domain layer if it does not appear in the raw or tool layers. The data in the domain layer should correctly reflect the tool layer's state.
How to reproduce
- Perform a Jira data sync with a longer time range.
- Set the
timeAfter for the next sync to a more recent time (to reduce the data range).
- Perform a full sync again.
- Observe that some outdated issues (outside of the time range set in Step 2) still remain in the domain layer (issues and board_issues tables), even though they do not exist in the raw and tool layers.
Anything else
It is suspected that the domain layer data for the corresponding scope is not being properly deleted during a full sync, leading to stale data remaining in the domain tables.

Version
main
Are you willing to submit PR?
Code of Conduct
Search before asking
What happened
After performing a full synchronization of Jira data, we found an issue that does not exist in the raw and tool layer tables. However, this issue is still present in the issues and board_issues tables in the domain layer.
What do you expect to happen
The issue should not exist in the domain layer if it does not appear in the raw or tool layers. The data in the domain layer should correctly reflect the tool layer's state.
How to reproduce
timeAfterfor the next sync to a more recent time (to reduce the data range).Anything else
It is suspected that the domain layer data for the corresponding scope is not being properly deleted during a full sync, leading to stale data remaining in the domain tables.
Version
main
Are you willing to submit PR?
Code of Conduct