narrowizard opened a new issue, #8330:
URL: https://github.com/apache/incubator-devlake/issues/8330

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### 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
   
   1. Perform a Jira data sync with a longer time range.
   2. Set the `timeAfter` for the next sync to a more recent time (to reduce 
the data range).
   3. Perform a full sync again.
   4. 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.
   
   
![Image](https://github.com/user-attachments/assets/4fcae32c-3f30-4cc0-b00c-0f8f44106c2b)
   
   ### Version
   
   main
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to