jdcasey hit a bug where:

• He had some issues copied by sync2jira nicely.
• Some of them were duplicates in jira, so he marked them as duplicates and closed them.
• When sync2jira restarted, it look for any unmapped tickets it had missed. It saw that those few were missing and it recreated them.
• jdcasey saw that issues he had previously closed mysteriously reappeared, and now we're afraid he's going to lose his mind. Help us!

The short fix here will be to add detection of duplicates to the get_existing_jira_issues function here: https://pagure.io/sync-to-jira/blob/master/f/sync2jira/downstream.py#_29-41

A much much better solution would be to add something in jira where we can add a url for an external issue tracker.

Then, we can uniquely identified sync2jira tracked issues there, and make our mapping much less fragile.