尝试了 redmine 和 trac，但它们都不允许我在项目之间共享里程碑和错误
你知道 redmine 或 trac 的一个好的替代品可以实现这样的功能吗？我也尝试过fogbugz，但是与svn存储库浏览的集成太差（并且没有代码审查支持的迹象）。
Do you know a good alternative to redmine or trac which allows such a feature? I've also tried fogbugz, but is too poorly integrated with the svn repository browsing (and there is no sign of code review support).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
抱歉，但我不认为有“Redmine 的良好替代品”，它是一个很好用的系统。
我不太确定到底是什么推动了您的需求，所以我唯一的建议是查看 Redmine 上的子项目支持。对于您想要共享错误和里程碑的所有项目，设置一个顶级项目，然后各个项目可以是该主伞项目下的子项目。
如果一个问题对于许多项目来说是常见的，那么在顶级项目中创建它，特定于一个项目的问题然后在子项目中创建它，顶层的过滤可以设置为显示子项目中的所有问题以及主要项目。
Redmine 对所有问题都有唯一的编号，因此在票证或 wiki 中，您可以轻松地跨项目交叉引用票证。
如果这没有帮助，那么我认为您将进入编写自己的插件的领域。
Sorry but I don't think there is "a good alternative to Redmine", it's good useable system.
I'm not too sure what exactly is driving your requirements, so my only suggestion would be to look at the sub project support on Redmine. For all your projects where you want to share bugs and milestones set up a top level project, the individual projects can then be sub projects under this main umbrella project.
If an issue is common to many projects then create it in the top project, issues specific to one project then create it in a sub project, the filtering at the top level can be set to display all the issues from the sub projects as well as the main project.
Redmine has unique numbering for all issues so in the tickets or the wiki you can cross reference tickets across projects quite easily.
If that doesn't help then I think you'll be into the realms of writing your own plugin.
您可能需要考虑使用 Trac 和 Ticket Mover 插件，该插件还允许复制或移动门票和其他 Trac 元素，包括里程碑。
这不是一个完美的解决方案，因为您需要将编辑迁移到里程碑，但我们发现它在与您类似的情况下很有用，其中里程碑是不同的，但错误/功能有时需要跨多个项目解决。
You might want to consider Trac with the Ticket Mover plugin, which also allows the copy or move of tickets and other Trac elements, including milestones.
Not a perfect solution, as you need to migrate edits to the milestones, but we've found it useful in a situation similar to yours where milestones were distinct, but bugs/features occasionally required resolution across multiple projects.