It's unusual, but it is possible for the JIRA index to get into a state where queries return the wrong results and this can cause sync2jira to create many duplicate issues because it doesn't realize that the JIRA issues are already there.
There are a few potential approaches to this...
Test to see if the indexer is in a bad state. Do a query where you know what the results should be and abort if you get different results.
Maintain a history of sync2jira operations and use that history when choosing what new issues need to be copied.
Set some kind of heuristic such as "if sync2jira find more than 50 issues in pagure that need to be copied to JIRA, then something is probably broken"
Let's try approach 1. We could do a query on startup for "all issues in JIRA" and if it returns zero issues, then something is busted.
PR #97 addressed this issue. Closing this issue.
Metadata Update from @sidpremkumar: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.