Investigate idempotency options for the JIRA issues import

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Ideally if import would be triggered more than one time, we would want to start importing from where last import finished. As an alternative we could start over but skip issues that were already importied by storing an external issue identifier, i.e. add a import_id: string column to issues table. I think we should settle on string value as not all systems would have an integer identifier.

Edit: Or just store last imported issue ID and timestamp in import data and ignore anything imported before that.