This repository should be migrated to [forgejo](https://forge.fedoraproject.org) as part of migrating all Fedora Quality repositories.

This repository DOES NOT have CI, which makes the migration more straightforward. But it's our primary ticket tracker, so we want to preserve all tickets (including numbers) as part of the migration, and ideally have common pagure.io URLs redirect to the appropriate forge.fp.o URL.

Note [server WG migrated already](https://forge.fedoraproject.org/server/tickets/issues) so we could ask how that got done and any advice from it.

List of issues (or reason I didn't creat an issue) for other fedora-qa repos:

• autocloudreporter - OBSOLETE
• https://pagure.io/fedora-qa/autococonut/issue/15
• autoqa - OBSOLETE
• beaker-tools - OBSOLETE
• https://pagure.io/fedora-qa/blockerbugs/issue/295
• https://pagure.io/fedora-qa/blocker-review/issue/2009
• https://pagure.io/fedora-qa/check-compose/issue/3
• cloud-atomic-ansible-tests - OBSOLETE
• commitfinder - OBSOLETE
• https://pagure.io/fedora-qa/createhdds/issue/16
• https://pagure.io/fedora-qa/fedfind/issue/27
• fedora-beaker-tests - OBSOLETE
• fedora-desktop-testing - OBSOLETE
• https://pagure.io/fedora-qa/fedora-glossary/issue/1
• fedora-gooey-karma - ARCHIVED
• fedora-kiwi-instance-docs - OBSOLETE
• https://pagure.io/fedora-qa/fedora_openqa/issue/114
• https://pagure.io/fedora-qa/fedora-release-autotest/issue/1
• fedora-tcms-migration - OBSOLETE
• fedora-testcases - OBSOLETE
• https://pagure.io/fedora-qa/flask_skeleton/issue/2
• kanban - OBSOLETE?
• landingpage - OBSOLETE
• lolz_and_roffle - OBSOLETE
• modularity_testing_scripts - OBSOLETE
• motd - OBSOLETE(? - I think - think it's related to landingpage)
• https://pagure.io/fedora-qa/openqa_classifier/issue/1
• openqa_docker - OBSOLETE
• https://pagure.io/fedora-qa/openQA_scripting_tool/issue/1
• https://pagure.io/fedora-qa/openqa_testdata/issue/2
• https://pagure.io/fedora-qa/oraculum/issue/221
• oraculum-client - OBSOLETE / NOT IMPLEMENTED?
• https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/446
• https://pagure.io/fedora-qa/packager_dashboard/issue/187
• phabarchive - ARCHIVED; probably not needed since we have https://fedorapeople.org/groups/qa/phabarchive/
• https://pagure.io/fedora-qa/_private/issue/37
• https://pagure.io/fedora-qa/python-ci_messages/issue/2
• https://pagure.io/fedora-qa/Python-OpenQA-needle-editor/issue/7
• https://pagure.io/fedora-qa/python-wikitcms/issue/12
• https://pagure.io/fedora-qa/qa-docs/issue/9
• qa-make - OBSOLETE? I don't think we're still using this?
• https://pagure.io/fedora-qa/qa-misc/issue/10
• https://pagure.io/fedora-qa/qa-stats/issue/3
• https://pagure.io/fedora-qa/releasestream/issue/8
• https://pagure.io/fedora-qa/relval/issue/48
• https://pagure.io/fedora-qa/relvalconsumer/issue/7
• https://pagure.io/taskotron/resultsdb_conventions/issue/6
• switchcheck - OBSOLETE
• taskotron-fedora-cloud-tests - OBSOLETE?
• testcase-playbook - OBSOLETE / unpopulated
• https://pagure.io/fedora-qa/test_cases/issue/2
• https://pagure.io/fedora-qa/testdays/issue/3
• https://pagure.io/fedora-qa/testdays-web/issue/69
• uf-monitor - OBSOLETE
• windows-ad-integration-testing - probably OBSOLETE? we eventually implemented the 'AD' testing using Samba