I think you need to look at what you're trying to accomplish, what functionality will help you accomplish those goals and how that matches up with the available options, and look at the flexibility the system provides.
I think flexibility is where Trac really shines -- trac-hacks has a lot of plugins to add a lot of functionality (some better than others), and they aren't difficult to write; and the workflow is very configurable so it can match what you want your workflow to be. You can make it very simple (a ticket is either open, or it's closed), or as complex as you can devise, with side-effects at certain transitions, etc.
You can also ask questions in #trac on freenode; it's pretty low noise, and there are generally a couple people around during US business hours who can answer questions and discuss Trac stuff with you.
To really compare the various options, I'd suggest setting up a small example project in each, play around with it, and ask questions. But you really need to decide what matters to you to even get started.
发布评论
评论（3）
预先披露：我是 Trac 开发人员之一。
我认为您需要看看您想要完成什么，哪些功能将帮助您实现这些目标以及它如何与可用选项相匹配，并查看系统提供的灵活性。
我认为灵活性是 Trac 真正的亮点 - trac-hacks 有很多插件可以添加很多功能（有些比其他更好），而且它们并不难写；而且工作流程是非常可配置的，因此它可以匹配您想要的工作流程。您可以使其变得非常简单（票证要么打开，要么关闭），也可以设计得尽可能复杂，在某些转换中产生副作用等。
您还可以在 freenode 上的 #trac 中提问；噪音非常低，而且在美国工作时间周围通常会有几个人可以回答问题并与您讨论 Trac 的内容。
为了真正比较各种选项，我建议在每个选项中设置一个小示例项目，试用它并提出问题。但你确实需要决定什么对你来说最重要才能开始。
Up-front disclosure: I'm one of the Trac devs.
I think you need to look at what you're trying to accomplish, what functionality will help you accomplish those goals and how that matches up with the available options, and look at the flexibility the system provides.
I think flexibility is where Trac really shines -- trac-hacks has a lot of plugins to add a lot of functionality (some better than others), and they aren't difficult to write; and the workflow is very configurable so it can match what you want your workflow to be. You can make it very simple (a ticket is either open, or it's closed), or as complex as you can devise, with side-effects at certain transitions, etc.
You can also ask questions in #trac on freenode; it's pretty low noise, and there are generally a couple people around during US business hours who can answer questions and discuss Trac stuff with you.
To really compare the various options, I'd suggest setting up a small example project in each, play around with it, and ask questions. But you really need to decide what matters to you to even get started.
这些页面可能会有所帮助：
维基百科：项目管理软件比较
维基百科：问题跟踪系统的比较
These pages might be helpful:
Wikipedia: Comparison of project management software
Wikipedia: Comparison of issue-tracking systems
是的，我会建议同样的事情；让我们大家都去尝试一下，并实际使用每一个。这是真正决定它是否是您所需要的唯一方法。
Yes I would suggest the same thing; give us all a go, and actual use each. That is the only way to really decide if it is what you need.