It couldn't matter less to me what technology the bug tracker is built in. I like FogBugz alot, and it's not .Net based. Neither is Bugzilla, and we've used that to track .Net projects.
There's really no point in worrying about the underlying technology of the tools you need to do your job right.
Several of the other answers say that it doesn't matter what the system is written in, and i can't agree with that.
They are probably right when it comes to simple desktop applications (for example, we use Mercurial/TortoiseHG for source control and it really doesn't matter that it's written in Python...it just works).
But it's completely different when the application needs some kind of special server (web server, database server...most available bug trackers need both). When you need some of those, you will probably use something you know:
For example, we are a Microsoft shop...we already have ASP.NET web servers and SQL servers ready and running and we have people who know how to use them. On the other hand, there's no one here who knows anything about, say, Oracle/MySql/PostgreSql or Ruby/PHP.
This rules out quite a lot of the available bug trackers because we have no idea to even get them to run!
Yes, we could try & error and setup new web and database servers and try to get the stuff working, but it's hard to justify learning all the stuff just to run a simple bug tracker. (and just installing and getting it to run is not all you need...for example, when you have the database running, someone has to figure out how to take backups, how to restore them in case something goes wrong...the list goes on and on)
So we will probably use a .net bug tracker (we are just evaluating ourselves)...probably Bugtracker.Net.
EDIT:
John, that's not what I meant.
For example, besides Bugtracker.Net I evaluated Redmine as well (which is written in Ruby on Rails). I don't want to change anything in the Redmine code, just install it - but take a look at the installation instructions: Even to get Redmine installed, you need a certain level of knowledge about RoR (which I don't have at all, neither any of my co-workers - we are Windows and .net users and no one of us has ever used Ruby). Maybe Redmine is cooler than BugTracker.Net or can do more - but can we really justify learning some RoR just to be able to install this one piece of software?
You forgot FogBugz. I don't think it's entirely in .net but parts of it definitely is.
Also I am the same when looking for open source options. I look for .net products first because I know how they work. With closed source options or hosted options I don't care much.
I've recently been tasked with getting an open source bug tracking system up for my company. I looked through many of the commercial and open source systems available and finally settled on BugTracker .NET, which is free.
I am definitely happy with my decision. The system is very feature rich, especially in the email notifications area. But the part that I like about it the most is it's flexibility. My bosses wanted tons of different changes done to it when I first demoed the app to them. Amazingly 99% of the changes didn't require me to write any code, they were either settings in the admin config or the web.config. And for the coding modifications I did make I can say the app's code is certainly understandable and isn't too hard to modify if you need to (which you probably won't).
发布评论
评论（9）
对我来说，错误跟踪器采用什么技术构建并不重要。我非常喜欢 FogBugz，而且它不是基于 .Net 的。 Bugzilla 也不是，我们用它来跟踪 .Net 项目。
担心正确完成工作所需的工具的底层技术确实没有意义。
It couldn't matter less to me what technology the bug tracker is built in. I like FogBugz alot, and it's not .Net based. Neither is Bugzilla, and we've used that to track .Net projects.
There's really no point in worrying about the underlying technology of the tools you need to do your job right.
其他几个答案说系统用什么编写并不重要，我不能同意这一点。
当涉及到简单的桌面应用程序时，他们可能是正确的（例如，我们使用 Mercurial/TortoiseHG 进行源代码控制，它真的并不重要，它是用 Python 编写的......它只是工作）。
但当应用程序需要某种特殊服务器（Web 服务器、数据库服务器......大多数可用的错误跟踪器都需要）时，情况就完全不同了。
当您需要其中一些时，您可能会使用您知道的东西：
例如，我们是一家 Microsoft 商店...我们已经准备好并运行 ASP.NET Web 服务器和 SQL 服务器，并且我们有知道如何使用它们的人员.
另一方面，这里没有人了解 Oracle/MySql/PostgreSql 或 Ruby/PHP 等任何知识。
这排除了很多可用的错误跟踪器，因为我们甚至不知道如何让它们运行！
是的，我们可以尝试& 错误并设置新的网络和数据库服务器并尝试让这些东西正常工作，但是很难证明学习所有东西只是为了运行一个简单的错误跟踪器是合理的。
（仅仅安装并运行它并不是您所需要的……例如，当您运行数据库时，有人必须弄清楚如何进行备份，如何在出现问题时恢复它们……列表不胜枚举）
所以我们可能会使用 .net bug 跟踪器（我们只是评估自己）...可能是 Bugtracker.Net。
编辑：
约翰，这不是我的意思。
例如，除了 Bugtracker.Net 之外，我还评估了 Redmine（它是用 Ruby on Rails 编写的）。
我不想更改 Redmine 代码中的任何内容，只需安装它 - 但请查看 安装说明：
即使要安装 Redmine，您也需要一定程度的 RoR 知识（我根本没有，我的同事也没有——我们是 Windows 和 .net 用户，而且我们中没有人使用过 Ruby） .
也许 Redmine 比 BugTracker.Net 更酷或者可以做更多事情 - 但我们真的可以证明学习一些 RoR 只是为了能够安装这个软件吗？
Several of the other answers say that it doesn't matter what the system is written in, and i can't agree with that.
They are probably right when it comes to simple desktop applications (for example, we use Mercurial/TortoiseHG for source control and it really doesn't matter that it's written in Python...it just works).
But it's completely different when the application needs some kind of special server (web server, database server...most available bug trackers need both).
When you need some of those, you will probably use something you know:
For example, we are a Microsoft shop...we already have ASP.NET web servers and SQL servers ready and running and we have people who know how to use them.
On the other hand, there's no one here who knows anything about, say, Oracle/MySql/PostgreSql or Ruby/PHP.
This rules out quite a lot of the available bug trackers because we have no idea to even get them to run!
Yes, we could try & error and setup new web and database servers and try to get the stuff working, but it's hard to justify learning all the stuff just to run a simple bug tracker.
(and just installing and getting it to run is not all you need...for example, when you have the database running, someone has to figure out how to take backups, how to restore them in case something goes wrong...the list goes on and on)
So we will probably use a .net bug tracker (we are just evaluating ourselves)...probably Bugtracker.Net.
EDIT:
John, that's not what I meant.
For example, besides Bugtracker.Net I evaluated Redmine as well (which is written in Ruby on Rails).
I don't want to change anything in the Redmine code, just install it - but take a look at the installation instructions:
Even to get Redmine installed, you need a certain level of knowledge about RoR (which I don't have at all, neither any of my co-workers - we are Windows and .net users and no one of us has ever used Ruby).
Maybe Redmine is cooler than BugTracker.Net or can do more - but can we really justify learning some RoR just to be able to install this one piece of software?
我使用过BugNet，它是基于.NET的，实际上它似乎是基于旧版本的DotNetNuke 。
它并不完美，但它有效。 您可以在此处查看我的样式版本。
I have used BugNet, which is .NET based, actually it appears to be based on an older version of DotNetNuke.
It isn't perfect, but it works. You can see my styled version here.
好吧，总有BugTracker.NET...就
我个人而言，我并不关心系统是什么编写。只要它不是经典 ASP。 呃。
Well, there's always BugTracker.NET...
Personally, i don't really care what the system is written in. So long as it isn't Classic ASP. Ew.
您可能想尝试 EzSDLC http://encodesoft.com/?page_id=77 ，他们提供屏幕截图 pdf以及。 该工具基于 .NET
You might wanna try EzSDLC http://encodesoft.com/?page_id=77 , they provide screenshot pdf as well. The tool is .NET based
你忘了FogBugz。 我不认为它完全在 .net 中，但它的一部分肯定是。
在寻找开源选项时我也是一样。 我首先寻找 .net 产品，因为我知道它们是如何工作的。 对于闭源选项或托管选项，我不太关心。
You forgot FogBugz. I don't think it's entirely in .net but parts of it definitely is.
Also I am the same when looking for open source options. I look for .net products first because I know how they work. With closed source options or hosted options I don't care much.
还可以使用 Microsoft 的此问题跟踪器应用程序：[http: //www.asp.net/downloads/archived/starter-kits/issue-tracker/]
This Issue Tracker application from Microsoft can also be used: [http://www.asp.net/downloads/archived/starter-kits/issue-tracker/]
Fortress 的部分内容是用 .NET 构建的。
Parts of Fortress were built in .NET.
最近，我的任务是为我的公司建立一个开源错误跟踪系统。 我浏览了许多可用的商业和开源系统，最终选择了 BugTracker .NET，它是自由的。
我对我的决定非常满意。 该系统功能非常丰富，特别是在电子邮件通知区域。 但我最喜欢它的部分是它的灵活性。 当我第一次向他们演示该应用程序时，我的老板希望对其进行大量不同的更改。 令人惊讶的是，99% 的更改不需要我编写任何代码，它们要么是管理配置中的设置，要么是 web.config 中的设置。 对于我所做的编码修改，我可以说应用程序的代码当然是可以理解的，并且如果您需要的话（您可能不会）修改起来并不难。
I've recently been tasked with getting an open source bug tracking system up for my company. I looked through many of the commercial and open source systems available and finally settled on BugTracker .NET, which is free.
I am definitely happy with my decision. The system is very feature rich, especially in the email notifications area. But the part that I like about it the most is it's flexibility. My bosses wanted tons of different changes done to it when I first demoed the app to them. Amazingly 99% of the changes didn't require me to write any code, they were either settings in the admin config or the web.config. And for the coding modifications I did make I can say the app's code is certainly understandable and isn't too hard to modify if you need to (which you probably won't).