将 Bugzilla 问题迁移到 github 问题跟踪器
我想将我的所有 Bugzilla 问题迁移到 github.com 上的问题跟踪器 (示例）（每个存储库都有一个问题跟踪器）。
1) 有工具吗？
2) 你是怎么做到的？
感谢您的建议，我会在最后写一个总结，我最终是如何做到的（希望如此）不是手动的！）
I would like to migrate all my Bugzilla issues to an Issue Tracker at github.com (Example) (you get an issue tracker per repository).
1) Are there tools out there?
2) How did you do it?
Thanks for any advices, I will write a summary at the end how I finally did it (hopefully not manually!)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
您需要从 Bugzilla 导出问题，然后使用 GitHub API 将问题上传到 GitHub：
http://developer.github.com/v3/issues/#create-an-issue
（请注意，通过 GitHub 支持渠道导入的旧问题已停止） >
这确实意味着您的问题编号会发生变化，因此您可能需要在问题描述中附加“Bugzilla-Id”页脚，这样您就可以使用 GitHub 的问题自由文本搜索从旧的 Bugzilla id 中查找它们。
至于从 Bugzilla 导出数据，我认为您的选择是：
祝你好运！如果您确实编写了导出脚本，我鼓励您在 GitHub 上将其开源！
You need to export your issues from Bugzilla, and then use the GitHub API to upload the issues into GitHub:
http://developer.github.com/v3/issues/#create-an-issue
(note that the old issue-import through GitHub support channels is discontinued)
This does mean your issue numbers will change, so you might want to append a 'Bugzilla-Id' footer to your issue description, so you can use GitHub's free-text search on issues to find them from the old Bugzilla ids.
As far as exporting your data from Bugzilla goes, I think your options are:
Good luck! If you do write an export script, I'd encourage you to open-source it on GitHub!
我最近在尝试将 W3C 项目的 Bugzilla 问题迁移到 GitHub 时遇到了同样的问题，所以我最终
我希望我的脚本也可以轻松修改以适应您的目的。
I recently encountered the same problem trying to migrate Bugzilla issues of a W3C project to GitHub, so I ended up
I hope that my script can be easily modified to fit the purposes of you, too.
去年我写了一个 Perl 脚本来处理这个问题；您可以通过 Bugzilla 的内置 UI 将所需的错误有效地保存为 XML，并且脚本将它们作为单独的问题上传。
它使用 Net::GitHub::V2 进行上传 API 并使用 GitHub 的 oauth 系统进行身份验证。默认情况下，它从环境中读取用户和存储库配置，因为我是从其他脚本运行它的；但如果您想自定义，所有变量都位于脚本的顶部。
https://github.com/rowanj/BugzillaMigrate
I wrote a Perl script to handle this last year; effectively you save the bugs you want as XML via Bugzilla's built-in UI for it, and the script uploads them as individual issues.
It uses
Net::GitHub::V2for the uploading API and GitHub's oauth system for authentication. It reads the user and repo config from the environment by default because I was running it from other scripts; but all the variables are at the top of the script if you want to customise.https://github.com/rowanj/BugzillaMigrate
您可以在 Bondable 的帮助下做到这一点
https://web.archive.org/web/20160304172242/http://www.bondable.com/integrations/p/services/bugzilla" archive.org/web/20160304172242/http://www.bondable.com/integrations/p/services/bugzilla
您实际上可以与 Bugzilla 创建大量集成
注意：截至 2020 年 3 月 11 日，www.bondable.com 不再托管 Web 应用程序，并且原始链接是垃圾邮件
You can do that with the help of Bondable
https://web.archive.org/web/20160304172242/http://www.bondable.com/integrations/p/services/bugzilla
You can actually create a lot of integrations with Bugzilla
Note: As of 2020-03-11, www.bondable.com is no longer hosting a web app, and the original link is spammy