Bugtrackers: be resistant to replication issues
When the destination tracker is unavailable (service down, network issue, ...), replication will fail. However, since we now only poll issues when they have changed, this means the replication may not happen until the source bug gets updated.
My proposal is to add a field to the bug model to indicate a replication failure and thus force it to get re-polled on the next round.