基于每个项目的错误跟踪
一直在研究错误跟踪解决方案。搜索了网络、其他网站以及其他答复/问题，
我有一个项目，该项目将有多个子项目。每个子项目都需要有自己的错误跟踪空间。即，项目A、项目B和项目C将由不同的人处理，并将产生需要由开发人员解决/跟踪的不同问题/错误。
快速浏览一下免费工具（bugzilla/mantis/等..），不确定是否有一种快速/简单的方法来创建满足我的需求的解决方案。
我正在考虑有大约 200-300 个子项目，每个子项目有 1-2 个开发人员..
不能收费，因为这是一个小型/没有资金的运营，并且该项目将拥有超过开发人员/子项目的数量由收费应用程序的免费操作指定。
感谢想法/评论。
谢谢
been looking into bug tracking solutions. searched the net, other sites, as well as other replies/questions here,
i've got a project that will have multiple subprojects. each subproject will have a need to have its' own bug tracking space. ie, projectA, projectB, and projectC will be worked on by different people, and will generate different issues/bugs that need to be resolved/tracked by the devs.
in taking a quick look at the free tools, (bugzilla/mantis/etc..) not sure if there's a quick/easy approach to creating a solution for my needs.
i'm looking at having ~200-300 subprojects, each with 1-2 devs..
can't go fee based, as this is a small/not funded operation, and the project will have more than the number of devs/subprojects specified by the free operations from the fee based apps.
thoughts/comments are appreciated.
thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们在工作中就遇到过这种情况，在评估了所有选项后，决定使用 Redmine。 Redmine有多个项目的概念，每个项目都有自己的错误和功能跟踪器、wiki空间、版本控制集成、文档存储、新闻提要等。项目也可以分层嵌套，这是一个非常好的功能。您还可以设置项目路线图并将功能链接到特定版本。
您可以设置自定义角色，开发人员可以对其所属的每个项目拥有不同的项目管理权限。
我最喜欢的功能是源代码管理集成。能够将错误链接到各个 SVN 提交真是太好了，并且单击查看差异确实很有帮助。
该代码是使用 Ruby on Rails 和数据库后端（我们使用 MySQL）实现的。它是我们的生产错误跟踪器，并且非常可靠。该项目本身使用 Redmine 进行自己的错误跟踪。它得到了良好的支持，开源，并且在我们使用它的两年中取得了稳步的进步和改进。
如果您想先了解一下 Redmine 的功能，可以先看一下交互式演示站点你自己下载。
We had exactly this situation at work, and after evaluating all the options, decided to go with Redmine. Redmine has the concept of multiple projects, each with their own bug and feature tracker, wiki space, version control integration, document storage, news feed, etc. The projects can be hierarchically nested as well, which is a really nice feature. You can also set up project roadmaps and link features to specific releases.
You can set up custom roles, and developers can have different project management rights for each project they are a member of.
My favourite feature is the source code management integration. It's great to be able to link bugs to individual SVN commits, and clicking through to see the diff is really helpful.
The code is implemented using Ruby on Rails, with a DB backend (we use MySQL). It is our production bug tracker, and has been very reliable. The project itself uses Redmine for it's own bug tracking. It is well supported, open source, and there has been steady progress and improvements in the 2 years we have been using it.
There's an interactive demo site that you can have a look at, if you want to get a feel for Redmine's capabilities before you download it yourself.
Bugzilla 有一个“严格隔离”模式，这使得它对组安全非常关注。每个子项目都可以有自己的小组，该小组对于这些开发人员来说是不同的。
或者，您可以使用相同的安装但具有多个数据库：
http://www.bugzilla.org/docs/3.6/en/html/multiple-bz-dbs.html
Redmine（或类似的）可能是您想要的更好的选择，但这就是您的方式在 Bugzilla 中执行此操作。
Bugzilla has a "strict isolation" mode that makes it anal about group security. Each subproject could have its own group that's distinct to those devs.
Alternatively, you could use the same installation but with multiple databases:
http://www.bugzilla.org/docs/3.6/en/html/multiple-bz-dbs.html
Redmine (or similar) might be a better alternative for what you want, but that's how'd you do it in Bugzilla.