We have quite a lot of tools, you can find references to all of them (I hope!) at https://fedoraproject.org/wiki/QA/Tools . We should check through the source for each project and look for references to Trac, and update them to refer to Pagure instead. You'll need to send either Phabricator diffs or Pagure pull requests for changes to the projects (each one should mention which system it uses in the README or so); Pagure pull requests are pretty easy and work like github, Phabricator is a bit more complicated to get set up the first time, there is a guide at https://fedoraproject.org/wiki/User:Tflink/taskotron_contribution_guide and you can always ask Tim, me etc. for help.
Facing an weird complication about exactly how to update a specific ticket which is not fedora-qa ticket and although their project has been migrated to pagure , but this specific ticket hasn't been. Example https://pagure.io/taskotron/libtaskotron/blob/develop/f/libtaskotron/logger.py LOC 98. The line contains a ref to https://fedorahosted.org/koji/ticket/317 but even though the project has been migrated to pagure the ticket can no longer be traced https://pagure.io/koji/issues?status=all . Suggestion on how to deal with this will be helpful.
For anything in Taskotron projects, please file a new issue (so e.g. for libtaskotron create a ticket in Phab against libtaskotron project). If you can trace the tickets, add the new link, it will help. If you can't (in this particular case I believe the ticket was not migrated because it's closed), just say you couldn't, and we will deal with that. Thanks.
@kparal I have filed a issue --> https://phab.qa.fedoraproject.org/T910
Metadata Update from @sumantrom: - Assignee reset - Issue priority set to: None (was: 2)
@sumantrom, I see you reset the assignee. Is there anything else to do (except for resolving the T910 issue)? If not, please close the ticket.
@kparal I am keeping this ticket open until @a2batic and me have gone through all the files and in QA tools and taskotron repos in pagure which might have a reference pointing to trac.
OK, so, does it make sense to keep you assigned to this? That indicates that no other people should start working on this instead, because it's your task.
Metadata Update from @a2batic: - Issue assigned to sumantrom
Done :)
The migration is completed successfully ! Thanks to @a2batic and all who helped . Closing this one.
Metadata Update from @sumantrom: - Issue status updated to: Closed (was: Open)
Metadata Update from @sumantrom: - Issue close_status updated to: Fixed
Login to comment on this ticket.