Hi,
Have you considered migrating from Bugzilla to GitHub Issues? I think co-locating issues, code, and PRs at GitHub would make it easier to browse both issues and code. I guess many Tomcat users browse code (including Tomcat code) in GitHub, and they would likely use GitHub PRs (Tomcat PRs and PRs for the other projects). It is inconvenient to require Bugzilla login for the sole purpose of filing an issue. It is inconvenient that search over bugs is disconnected from search over code. If bugs are migrated to GitHub, then a single GitHub search would work for everything: code, issues, PRs GitHub allows richer comment formatting (e.g. code highlight). GitHub shows code preview when you mention link to code in an issue comment. Moving issues to GitHub would unlock cross-references between projects (e.g. users could mention Tomcat issues) so others can see which projects reference the same issue, and sometimes you could peek into the workarounds. I'm working on migrating Apache JMeter (Bugzilla -> GitHub Issues), see https://lists.apache.org/thread/xmccss17s6sm8wzcm56d7sr6py663s7w , and I have a migration script https://github.com/vlsi/bugzilla2github It preserves bugs, comments, attachments, and links between bugs. Here's a recent dry-run for JMeter: https://github.com/vlsi/tmp-jmeter-issues For reference, the first bug in JMeter was filed on 2003, and we look forward to migrating all the ~5K bugs to GitHub issues. LLVM moved from Bugzilla to GitHub a year ago (50K bugs since 2003) WDYT? Vladimir
