问题/缺陷跟踪软件
我们的团队目前正在审查我们的工具集，并寻找除源控制和项目管理软件之外的新缺陷/问题跟踪软件。
对于问题跟踪，我们查看了 bugzilla、fogbugz、bugtracker.net、sourcegear fortres 和 bugnet。
我对我们列出的列表并不满意，所以我很想知道其他人在使用什么。
为了安全起见，我们正在寻找 Active Directory 集成，尽管我们会选择 Windows 应用程序，但 Web 界面可能会更优惠，Visual Studio 集成也是一个额外的好处。 我们需要对缺陷进行优先级排序，标记发现缺陷的版本，标记修复缺陷的版本，并希望能够围绕每个问题/缺陷保持讨论。 我们还希望将项目分类为缺陷、增强请求等，并记录缺陷的解决方法。
非常相似的问题：
Our group is currently reviewing our toolset and looking for new defect/issue tracking software in additional to source control, and project management software.
For issue tracking, we've looked at bugzilla, fogbugz, bugtracker.net, sourcegear fortres, and bugnet.
I'm not satisfied with the list we've come up with, so I'm curios to know what others are using.
We're looking for Active directory integration for security, although we'd settle for a windows app, a web interface may be preferential, visual studio integration is also a bonus. We need to prioritize defects, mark the version the defect was found in, mark the version the defect was fixed in, and hopefully be able to maintain a discussion around each issue/defect. We'd also like to categorize items as defect, enhancement request, etc. and document workarounds for defects.
Very similar question:
https://stackoverflow.com/questions/101774/what-is-your-bug-task-tracking-tool
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
尝试解开。 如果您使用他们的版本控制托管（SVN 和 Git 选项）及其问题跟踪器，您会得到一些很好的集成内容。 例如，您可以在提交消息中输入一条注释，例如“fixes #384: Too much foo in the bar”*，您不仅可以将其变成问题的超链接，还可以将票证标记为已修复带有返回变更集的链接。 都是好东西。 这是一个基于 Web 的解决方案，由 Unfuddle 自己以 SaaS 类型的方式托管。
除此之外，为我过去使用过并且非常喜欢的 Trac +1。 从功能上来说，这是一个相当不成熟的项目，尽管它周围有一个非常健康的社区，已经开发了插件来完成很多额外的事情（比如你想要的 AD 身份验证）。 它也与许多源代码控制系统有类似的集成，但它的功能比 Unfuddle 的东西要少得多。 也就是说，您可以在提交消息中使用扩展的 wiki 语法，该语法在显示时由 Trac 解析以创建链接。 它不做 Unfuddle 所做的任何双向工作。 Trac 可用于内部托管； 或者，如果您希望托管它，Trac 的 wiki 上有可以执行此操作的地点列表。
*我一时记不起确切的格式。
Try Unfuddle. If you use their version control hosting (SVN and Git options) with their issue tracker, you get some good integration stuff going on. For example, you can enter a note in your commit message such as "fixes #384: Too much foo in the bar"*, and you not only get that turned into a hyperlink to the issue, but it also marks the ticket as fixed with a link back to the changeset. All good stuff. This is a web-based solution that is hosted by Unfuddle themselves, in a SaaS-type fashion.
Other than that, +1 for Trac which I've used in the past and like very much. It's quite an immature project feature-wise, although it's got a very healthy community around it that has developed plug-ins to do a lot of extra stuff (like the AD authentication you wanted). It also has similar integration with a number of source control systems, but it's much less feature-rich than the Unfuddle stuff. That is to say, you get to use an extended wiki syntax in your commit messages which is parsed by Trac when it's display to create links. It doesn't do any of the two-way stuff that Unfuddle does. Trac is available to host in-house; alternatively, if you want it hosted, there's a list of places that will do so on Trac's wiki.
*I can't remember the exact format off the top of my head.
在我们当前的项目中，我们令人惊讶地使用了 6 种不同的跟踪工具（PVCS 的 2 个版本），其中大部分是商业工具。 这是我对我们使用过的那些的看法。 我按照我最喜欢到最不喜欢的顺序列出了它们。
Serena Teamtrack - 我们使用网络客户端。 界面很直观。 性能因安装而异，但与每个工具中的相同数据相比，此方法运行速度最快。 它也适用于 Firefox。
HP 质量中心 - 这也是基于 Web 的，但仅限 IE。 从好的方面来说，它组织良好、易于使用且功能齐全。 它对我们来说也有合理的性能。
它有一个奇怪的功能，就是没有保存按钮。 它会自动为您保存。 要强制保存，您必须导航到另一张票证。 另外，当你第一次使用它时，它必须安装如此多的DLL，以至于它实际上是一个胖客户端。 在这种情况下，IE 有时会被锁定（通常是在会话过期后尝试重新初始化会话时）。 一旦锁定，您有时必须杀死 IE 才能重新获得控制权。
Bugzilla - 我没有像其他工具那样彻底地使用它，所以这不是一个公平的比较。 我们短暂地用它来处理一些内部门票。 我认为最大的好处是（缺乏）成本。 IMO，我只是没有发现该界面像其他工具那样漂亮且易于使用。 已经有一段时间了，所以我为缺乏细节而道歉，为什么我将它降级为其他。
Siebel - 除了比 PVCS 更好之外，他们的缺陷跟踪工具没有太多值得喜欢的地方。 界面看起来很做作。 就好像 Siebel 界面有一组用户界面控件，它试图将所有方钉强制插入其圆孔中。 另一个缺点是它使用冗长的生成 ID，因此很难引用它们或通过它们进行搜索。 除此之外，票证 ID 未排序。
Merant PVCS - 我们有独立的数据库并使用 Web 客户端和胖客户端。 现在已经有一段时间了，所以细节正在消失。 我记得该工具存在错误并且没有得到修复，例如报告无法显示某些字段。 表现很糟糕。 加载时间很长。 浏览门票的速度很慢。
On our current project, we've amazingly used 6 different tracking tools (2 versions of PVCS), mostly commercial. Here's my opinion on the ones that we've used. I've listed them in order of my most favored to least.
Serena Teamtrack - We use a web client. The interface is intuitive. Performance will vary across installations, but comparing with our same data in each tool, this works the fastest. It also works in Firefox.
HP Quality Center - This is also web based, but it is IE only. On the upside, it's well organized, easy to use, and full-featured. It has reasonable performance for us as well.
It has an odd feature where there isn't a save button. It saves automatically for you. To force a save, you have to navigate to another ticket. Also when you first use it, it has to install so many DLLs that it is practically a thick client. That being the case, IE sometimes gets locked up (usually when trying to reinitialize a session after session expiration). Once locked up, you occasionally have to kill IE to regain control.
Bugzilla - I didn't use this as thoroughly as the other tools, so this isn't a fair comparison. We used it briefly for some internal tickets. I suppose the big upside is the (lack of) cost. IMO, I just didn't find the interface as nice and easy to use as the other tools. Its been awhile so I apologize for lack of specifics for why I'm relegating it below the others.
Siebel - There wasn't much to like about their defect tracking tool apart from that it is better than PVCS. The interface seems hokey. It's as if the Siebel interface has a set of user interface controls and it tries to force all square pegs into its round holes. Another downside is that it uses lengthy generated IDs so its hard to reference them or search by them. Along with that, the ticket IDs aren't sequenced.
Merant PVCS - We had separate databases and used both the web client and thick client. Its been awhile now, so the details are fading. I recall there were bugs in the tool and they weren't getting fixed, for instance reports couldn't display certain fields. Performance was bad. It took a long time to load. It was slow to navigate through tickets.
支持问题跟踪与开发期间跟踪问题是不同的问题。
Trac http://trac.edgewall.org/ 是一个非常强大的工具，支持许多大型开放源项目。 您可以在 http://www.wush.net 等地方找到 Trac 托管
如果您需要更多工作流程和自定义， 出于安全考虑，您需要查看来自 Atlassian http://www.atlassian.com 的 JIRA。 Atlassian 有许多您可能也会觉得有用的产品。
对于支持设置中的问题跟踪，请尝试 RT http://bestpractical.com/rt。 RT 看似简单，但我见过它在最大的环境中使用，并且它可以很好地确保您对所做出的支持承诺负责。
Issue tracking for support is a different problem from tracking issues during development.
Trac http://trac.edgewall.org/ is a very capable tool which supports a number of large open source projects. You can find Trac hosting at places like http://www.wush.net
If you need more workflow and custom security, you'll want to look at JIRA which is from Atlassian http://www.atlassian.com. Atlassian has a number of products which you might also find useful.
For Issue tracking in a support setting, try RT http://bestpractical.com/rt. RT is deceptively simple, but I've seen it used in the largest environments and it does a good job making sure you are accountable to every you make a support commitment to.
具有您提到的所有功能的场外 (www) 托管解决方案是 NetResults Tracker
An off-site (www) hosted solution with all the features you mentioned is NetResults Tracker
我们使用 bugzilla，它非常适合我们。 我们没有调查太多其他的，因为老实说它满足了我们需要的一切，而且还有一些。
我们不使用 Visual Studio，所以我无法谈论集成兼容性。
We use bugzilla, it suits us perfectly. We haven't investigated too many others because honestly it does everything we need and then some.
We don't use Visual Studio so I can't speak for integration compatibility.
尝试一下 HappyFox (http://www.happyfox.com)，这是一个问题和错误跟踪软件。 简洁的界面和自动化功能可帮助您顺利跟踪和解决错误。 HappyFox 对于 2 名成员免费，对于较大的团队价格经济。
Try out HappyFox ( http://www.happyfox.com), an issue and bug tracking software. The clean interface and automation features help you track and resolve bugs smoothly. HappyFox is free for a 2 member and priced economically for larger teams.