Startrekzky opened a new issue, #5841: URL: https://github.com/apache/incubator-devlake/issues/5841
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement. ### Use case Some users found out that after an issue was deleted in Jira, the issue would not be deleted in DevLake after re-syncing the data, as Jira used the `incremental sync` by default to improve the speed. However, those users want to get rid of the deleted issues in DevLake. ### Description A solution to this is to: - [ ] Provide the blueprint configuration for users to choose which sync modes to use. According to the [supported data sources](https://devlake.apache.org/docs/next/Overview/SupportedDataSources), plugins that support the incremental sync should be supported: - [ ] GitHub - [ ] GitLab - [ ] Jira - [ ] TAPD - [ ] PagerDuty - [ ] Allow users to trigger an `empty and re-collect data` operation for a 'full refresh' mode blueprint. Users, especially those with a large data size don't need to fully refresh data every time as it takes time, they just need to remove the dirty data at a certain point, for example, the time before monthly/annual reporting. ### Related issues _No response_ ### Are you willing to submit a 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]
