Original reporter: rlerch@redhat.com

The issue:

Migrating this repo fails, it appears that when trying to make the issue, issue id 12 already exists for some reason.

```
2026/01/28 00:16:38 ...dels/issues/issue.go:913:insertIssue() [E] [Error SQL Query] INSERT INTO "gitea"."issue" ("repo_id","index","poster_id","original_author","original_author_id","name","content","content_version","milestone_id","priority","is_closed","is_pull","num_comments","ref","pin_order","deadline_unix","created","created_unix","updated_unix","closed_unix","is_locked") VALUES ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21) RETURNING "id" [495 12 -1 pacho2 923400 make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. I get this warning when trying to build with -j >1

Thanks! 0 0 0 true false 0 0 0 0 1552129818 1555180511 1555180510 false] - ERROR: duplicate key value violates unique constraint "UQE_issue_repo_index" (SQLSTATE 23505)
2026/01/28 00:16:38 ...ices/task/migrate.go:60:func1() [E] runMigrateTask[393] by DoerID[2] to RepoID[495] for OwnerID[2] failed: ERROR: duplicate key value violates unique constraint "UQE_issue_repo_index" (SQLSTATE 23505)
2026/01/28 00:16:38 ...ervices/task/task.go:55:handler() [E] Run task failed: ERROR: duplicate key value violates unique constraint "UQE_issue_repo_index" (SQLSTATE 23505)
```