Instead of looking for something that could integrate with Trac, maybe you could use a Trac based solution. Trac has some plugins for Scrum but I'd suggest to check out Agilo which is a nice Scrum oriented and polished version of Trac. This might be one of the best options in your case.
would i be incorrect to assert that you should go through http://trac-hacks.org first and then elaborate here what, if anything, you didn't like about the plugins you found there? otherwise it's not possible to really say what is the best approach, when it is unknown whether you've scanned through the easiest paths.
I work at a company that has completely embraced agile in our engineering organization, but we've done just fine using Jira for our issue management, even though it doesn't have any specific scrum features. Our product manager keeps user stories (fleshed out with acceptance criteria) in his own organized backlog. When the team picks them up for a sprint, he creates a Jira case and we put the case number on our board, along with all of the tasks (which aren't in Jira).
When bugs or feature requests come up (reported by customer support, netops, etc.), the PM prioritizes them just like any other user story. If they're of an immediate nature, he'll put them straight onto the board, but he's hesitant to do so, knowing that's really a redirection of resources. We leave some slack in our sprints to allow for such things, but if things get to hairy, we let him know that we'll have to drop a story, or not do the bugs.
发布评论
评论（3）
也许您可以使用基于 Trac 的解决方案，而不是寻找可以与 Trac 集成的东西。 Trac 有一些 Scrum 插件，但我建议查看 Agilo 这是一个Trac 的面向 Scrum 的优秀版本。这可能是您的情况的最佳选择之一。
Instead of looking for something that could integrate with Trac, maybe you could use a Trac based solution. Trac has some plugins for Scrum but I'd suggest to check out Agilo which is a nice Scrum oriented and polished version of Trac. This might be one of the best options in your case.
我断言您应该首先浏览 http://trac-hacks.org 然后再详细说明是不正确的您对在那里找到的插件有什么不满意的地方（如果有的话）？否则，当不知道您是否扫描了最简单的路径时，就不可能真正说出什么是最好的方法。
would i be incorrect to assert that you should go through http://trac-hacks.org first and then elaborate here what, if anything, you didn't like about the plugins you found there? otherwise it's not possible to really say what is the best approach, when it is unknown whether you've scanned through the easiest paths.
我工作的公司在我们的工程组织中完全采用了敏捷，但我们在使用 Jira 进行问题管理方面做得很好，尽管它没有任何特定的 Scrum 功能。我们的产品经理将用户故事（通过验收标准充实）保留在他自己组织的待办事项中。当团队选择他们进行冲刺时，他会创建一个 Jira 案例，我们将案例编号以及所有任务（不在 Jira 中）放在看板上。
当出现错误或功能请求时（由客户支持、netops 等报告），PM 会像任何其他用户故事一样对它们进行优先级排序。如果它们具有直接性，他会直接将它们放在董事会上，但他对此犹豫不决，因为他知道这实际上是资源的重新定向。我们在冲刺中留出一些余地来允许此类事情发生，但如果事情变得棘手，我们会让他知道我们将不得不放弃一个故事，或者不做错误。
I work at a company that has completely embraced agile in our engineering organization, but we've done just fine using Jira for our issue management, even though it doesn't have any specific scrum features. Our product manager keeps user stories (fleshed out with acceptance criteria) in his own organized backlog. When the team picks them up for a sprint, he creates a Jira case and we put the case number on our board, along with all of the tasks (which aren't in Jira).
When bugs or feature requests come up (reported by customer support, netops, etc.), the PM prioritizes them just like any other user story. If they're of an immediate nature, he'll put them straight onto the board, but he's hesitant to do so, knowing that's really a redirection of resources. We leave some slack in our sprints to allow for such things, but if things get to hairy, we let him know that we'll have to drop a story, or not do the bugs.