Synchronization between Github and Bountysource is broken

:lady_beetle: **Problem**

The existing bounty for https://github.com/kerel-fs/spectranalysis/issues/1 posted in [bs: 102888571-load-satnogs-artifacts](https://www.bountysource.com/issues/102888571-load-satnogs-artifacts) can't be claimed because bountysource is showing this issue as "open" while in fact it was already fixed&closed in github.

This is a synchronisation issue which happend multiple [(#1401)](https://github.com/bountysource/core/issues/1401) times [(#1474)](https://github.com/bountysource/core/issues/1474) in the past [(#1536)](https://github.com/bountysource/core/issues/1536).

I contacted support@ several weeks ago, but it is still not solved nor did I got a date when this will be fixed!

:bulb: **Possible solution**
- Add a working process to trigger the usage of the [existing admin tools](https://github.com/bountysource/core/issues/1474#issuecomment-638619641) to force close in the event of sync issues.
- Investigate the root cause for these synchronization issues

Start with the existing admin tools described in issue #1474 and compare the prior synchronization reports in #1401, #1474, and #1536. Investigate why a closed GitHub issue remains open in Bountysource; done means the root cause is addressed or a documented process reliably forces the bounty to close.

Written by the indexing model from the issue text.