Incidents data resolution statuses is incorrect

The reporting logic for the data in the incidents endpoint that lead to inaccurate statuses is now fixed and all data is back to normal.

Due to a migration on our backend, and a concept drift of one of the columns used to report on resolution statuses of incidents, most incidents currently have an unresolved status although they were resolved in the past.

We are working on correcting the business logic.