Get a $15/month account at wush.net and use it yourself for a while (no business relationship besides satisfied customer).
Bugzilla is powerful and has a lot of configuration options, which can be confusing.
I personally used it three years ago on a project I was working on. I had no project manager and I was the developer, so I needed a very-light-overhead systtem. Bugzilla gave me that. I put my main goal as an enhancement "productionalized system" and then I made dependencies to reach that point. I ended up having 160 nodes all dependent on each other. This essentially was a work breakdown structure. I didn't bother with time estimates, and I didn't bother with creating any other kind of project documentation.
A cool advantage was that as I coded, if I noticed something needed to be done, I would just pop it into bugzilla (20 second process once it's set up), tie it as a dependency, and go back to what I was doing.
Whenever I completed a task, I would look at the dependency diagram and find the outermost leaves (bugs that blocked other but weren't themselves blocked), and work at it.
The advantage of this method for me is that if a task had looked simple and had one node associated with it, but when doing the thing itself I realized it was more complex, I would just split it into different subtasks. This took only a minute and absolutely didn't involve a meeting with a project manager.
Other people on the team could track my progress by looking at open bugs, closed bugs sorted by dates, etc. They saw action, they left me alone. When I had external dependecies, I would make a bug, detail the work, and send that person a link via email. They could then see why this was needed by looking at the dependency diagram.
Note that unless previously agreed upon, I did not assign them the bug.
It worked really well and the system was ready one month early.
How will it work with SCRUM? Having only had a cursory glance at scrum I can't tell you. But that was my experience.
Using a dedicated host will allow you three things:
support
easy upgrades (unless you got gurus in-house, bugzilla management ain't easy--for me at least)
users across organizational boundaries.
Note that bugzilla has all sorts of security features, so it's easy to lock-down the users to what they need to see.
My stand-alone solution is DokuWiki + MantisBT + Subversion + Review Board, which can be integrated with relative ease. Hosted alternative is Bitbucket.org. The rationale is you write user stories on Wiki and can reference them specific tasks. Larger bugs can be collaboratively designed and the "wiki" link is provided on the bug report by Mantis. Review board lets you do peer code reviews against svn diff before change is committed.
Bugzilla Is a great bug tracking system. We have tried to use it for other project management tasks and the results are less then stellar. I would recommend finding something designed with your goals in mind.
发布评论
评论（4）
亲自尝试一下。
在 wush.net 上获得一个 15 美元/月的帐户并自己使用一段时间（除了满意的客户之外没有任何业务关系）。
Bugzilla 功能强大，并且有很多配置选项，这可能会让人感到困惑。
三年前，我在自己正在进行的一个项目中亲自使用过它。 我没有项目经理，而我是开发人员，因此我需要一个开销非常小的系统。 Bugzilla 给了我这个。 我将我的主要目标作为增强的“生产化系统”，然后我建立了依赖关系以达到这一点。 我最终拥有了 160 个相互依赖的节点。 这本质上是一个工作分解结构。 我没有费心去估计时间，也没有费心去创建任何其他类型的项目文档。
一个很酷的优点是，在我编码时，如果我注意到需要完成某些操作，我只需将其弹出到 bugzilla 中（设置完成后需要 20 秒处理），将其作为依赖项绑定，然后返回到我正在做的事情。
每当我完成一项任务时，我都会查看依赖关系图并找到最外面的叶子（阻止其他但本身没有被阻止的错误），然后进行处理。
对我来说，这种方法的优点是，如果一项任务看起来很简单并且有一个与之关联的节点，但在做这件事本身时我意识到它更复杂，我会将其拆分为不同的子任务。 这只花了一分钟，而且完全不需要与项目经理开会。
团队中的其他人可以通过查看未解决的错误、按日期排序的已关闭错误等来跟踪我的进度。他们看到了行动，他们让我独自一人。 当我有外部依赖性时，我会犯一个错误，详细说明工作，并通过电子邮件向该人发送链接。 然后他们可以通过查看依赖关系图了解为什么需要这样做。
请注意，除非事先同意，否则我不会将错误分配给他们。
效果非常好，系统提前一个月就准备好了。
它将如何与 SCUM 一起工作？ 我只是粗略地浏览了一下 scrum，所以无法告诉你。 但这是我的经历。
使用专用主机将为您带来三件事：
请注意，bugzilla 具有各种安全功能，因此很容易将用户锁定到他们需要查看的内容。
Try it for yourself.
Get a $15/month account at wush.net and use it yourself for a while (no business relationship besides satisfied customer).
Bugzilla is powerful and has a lot of configuration options, which can be confusing.
I personally used it three years ago on a project I was working on. I had no project manager and I was the developer, so I needed a very-light-overhead systtem. Bugzilla gave me that. I put my main goal as an enhancement "productionalized system" and then I made dependencies to reach that point. I ended up having 160 nodes all dependent on each other. This essentially was a work breakdown structure. I didn't bother with time estimates, and I didn't bother with creating any other kind of project documentation.
A cool advantage was that as I coded, if I noticed something needed to be done, I would just pop it into bugzilla (20 second process once it's set up), tie it as a dependency, and go back to what I was doing.
Whenever I completed a task, I would look at the dependency diagram and find the outermost leaves (bugs that blocked other but weren't themselves blocked), and work at it.
The advantage of this method for me is that if a task had looked simple and had one node associated with it, but when doing the thing itself I realized it was more complex, I would just split it into different subtasks. This took only a minute and absolutely didn't involve a meeting with a project manager.
Other people on the team could track my progress by looking at open bugs, closed bugs sorted by dates, etc. They saw action, they left me alone. When I had external dependecies, I would make a bug, detail the work, and send that person a link via email. They could then see why this was needed by looking at the dependency diagram.
Note that unless previously agreed upon, I did not assign them the bug.
It worked really well and the system was ready one month early.
How will it work with SCRUM? Having only had a cursory glance at scrum I can't tell you. But that was my experience.
Using a dedicated host will allow you three things:
Note that bugzilla has all sorts of security features, so it's easy to lock-down the users to what they need to see.
我的独立解决方案是 DokuWiki + MantisBT + Subversion + Review Board，可以相对轻松地集成。 托管替代方案是 Bitbucket.org。 基本原理是您在 Wiki 上编写用户故事并可以参考它们的特定任务。 可以协作设计更大的错误，并且 Mantis 的错误报告中提供了“wiki”链接。 审查板允许您在提交更改之前针对 svn diff 进行同行代码审查。
My stand-alone solution is DokuWiki + MantisBT + Subversion + Review Board, which can be integrated with relative ease. Hosted alternative is Bitbucket.org. The rationale is you write user stories on Wiki and can reference them specific tasks. Larger bugs can be collaboratively designed and the "wiki" link is provided on the bug report by Mantis. Review board lets you do peer code reviews against svn diff before change is committed.
我们在多个项目中非常成功地使用了 Trac 和 Subversion。
这里的主要优点是能够定制报告（其中一些非常特定于 Scrum），以便向管理层提供信息。
We've used Trac and Subversion very successfully for several projects.
The main advantage here is being able to tailor reports, some very Scrum specific, to provide information to management.
Bugzilla 是一个很棒的错误跟踪系统。 我们尝试将其用于其他项目管理任务，但结果并不理想。 我建议寻找一些根据您的目标而设计的东西。
Bugzilla Is a great bug tracking system. We have tried to use it for other project management tasks and the results are less then stellar. I would recommend finding something designed with your goals in mind.