FogBugz 案例正文中应包含哪些类型的信息？
在我工作的地方，我们一直在讨论 FogBugz 案例正文中应包含哪些类型的信息。我说的是当您创建新错误或在现有案例上按下“编辑”时，“打开者”文本下方的大型自由文本字段。
例如，我们都同意该错误的详细描述属于其中，并且当我们第一次创建错误时，我们通常会将该描述放入其中。但在以后的编辑中，哪些类型的信息可以/应该放置在那里？
我们意见不一的最大问题是设计讨论是否属于其中。像这样的事情：
FEATURE 714
Opened by 'Person A'
We need to provide a user with the ability to quiggle-fy the doodad.
Edited by 'Person B'
Do you think this will involve changing the crabbadonk interface as well?
Edited by 'Person C'
No, the crabbadonk is already quiggle-fied.
我们都同意 A 所说的内容属于那里，但我们不确定 B 和 C 之间的对话也属于那里是否有意义。
其他公司是做什么的？对于什么样的信息属于其中有什么普遍接受的原则吗？ FogBugz 有更好的地方吗？或者是否应该使用单独的工具？
We've been having a discussion, where I work, about what type of information should go in the body of a FogBugz case. I'm talking about the large free-text field just under the "Opened by" text when you create a new bug, or when you push Edit on an existing case.
For instance, we all agree that a detailed description of the bug belongs there, and we usually put that description in, when we first create a bug. But in later edits, what types of information can/should be placed in there?
The biggest issue that we don't all agree on is whether design discussion belongs in there. Something like this:
FEATURE 714
Opened by 'Person A'
We need to provide a user with the ability to quiggle-fy the doodad.
Edited by 'Person B'
Do you think this will involve changing the crabbadonk interface as well?
Edited by 'Person C'
No, the crabbadonk is already quiggle-fied.
We all agree that what Person A said belongs there, but we're unsure of whether it makes sense for the conversation between Person B and Person C to be in there as well.
What do other companies do? Is there any generally accepted principles for what kind of information belongs in there? Is there a better place in FogBugz for that? Or is there a separate tool that should be used for it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
对于 FogBugz，我喜欢对我的项目做以下事情：
这具有使用各种“格式”的优点以它们最好的方式工作，并且还提供了很多灵活性。如果您需要能够在事物之间来回链接，已经有一些插件可以使这变得简单，并且编写您自己的插件并不太难（无论是作为 bugmonkey 脚本还是完整的插件。）
For FogBugz, here is what I like to do with my projects:
This has the advantage of using the various "formats" in the way they work best, and also provides a lot of flexibility. If you need to be able to link back and forth between things, there are plugins already that make this easy, and writing your own isn't too tough (either as a bugmonkey script or a full plugin.)