版本控制与错误跟踪软件的集成有多重要 [英] How important is version control integration with your bug tracking software

问题描述

目前我们使用 FogBugz 来跟踪问题并发现它没问题.我正在寻找其他可以让最终用户能够与我们一起跟踪他们的案例的东西.和一些实际上适用于电子邮件的东西.我找到了一些支持这些功能的替代方案，但它们没有与版本控制集成.我们已经在fog bugz 中获得了所有的SVN 钩子并且我们使用了它们——但我还没有真正发现它们都那么有用.有没有人发现需要将版本控制与错误跟踪器集成的一个很好的理由?

Currently we use FogBugz for tracking issues and found it to be ok. I'm looking for something else that can allow end users the ability to track their cases along with us. And something that actually works well with email. I've found a few alternatives that support those features but they don't integrate with version control. We've got all the SVN hooks in fog bugz and we use them - but I haven't really found them all that useful. Has anyone found a really good reason to need version control integration with the bug trackers?

推荐答案

显然，这种集成对于软件的运行来说并不是必不可少的.通过一些纪律，每次签入都可以手动附带一个错误编号，并且每个错误解决方案都可以手动添加一个版本控制标签.

Clearly, this kind of integration is not something that is essential to the operation of the software. With a bit of discipline every check-in can be accompanied with a bug number manually, and every bug resolution can manually have a version control tag added to it.

然而，在其他条件相同的情况下，我个人总是更喜欢自动化而不是用户纪律"，因为后者迟早会不时让您失望.不是因为用户有恶意或无能，而是因为人们无法始终保持 100% 的警惕.

All else being equal however, I personally will always prefer automation over 'discipline of the users', because the latter will always sooner or later let you down from time to time. Not because the users are malicious or incompetent, but simply because people cannot be 100% alert all of the time.

这篇关于版本控制与错误跟踪软件的集成有多重要的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！