http://our.fogbugz.com/default.asp?W977
I suspect it will be a simple task, but just thought I would ask before I tried it.
我怀疑这将是一项简单的任务,但我想在尝试之前我会问。
If you have used it, how did it go? Any caveats or things to help? Can the changes be undone automatically?
如果您已经使用过它,它是怎么回事?任何警告或事情要帮助?可以自动撤消更改吗?
Anything you would have done differently or configured in trac beforehand to make it go easier?
你有什么不同的事情或事先在trac中配置,以使它变得更容易?
By the way: I am pleased with my initial trial of fogbugz, Nothing wrong with trac, but I really wanted an autoresponder and a way for emails to support@mycompany.com to create a new ticket and reply. It is just so professional.
顺便说一下:我很满意我对fogbugz的初步试用,trac没什么问题,但我真的想要一个自动回复器和电子邮件到support@mycompany.com创建新票和回复的方式。它非常专业。
Curious about the project estimation, but that was not a factor. I am looking forward to trying that.
对项目估算感到好奇,但这不是一个因素。我期待着这样做。
1 个解决方案
#1
I tried it and it choked on our Wiki pages. I wasn't particuarly excited about the way the import tool mapped the Trac fields to the FogBugz fields.
我尝试了它,它在我们的维基页面上窒息。我对导入工具将Trac字段映射到FogBugz字段的方式感到特别兴奋。
Another issue is that you can't really delete issues once they're in FogBugz, so after the first failed import I just closed my Student & Startup account and opened a new one.
另一个问题是,一旦他们进入FogBugz就无法真正删除问题,因此在第一次失败导入后,我只关闭了我的学生和启动帐户并开了一个新帐户。
I ended up transferring our ~100 bugs manually because I decided too many of them were stale and it was worth the time it took to personally look at each one and rethink the priority. If you have more bugs or aren't at a point in your project where stepping back and looking at the whole To-Do list in that way would make sense, that might not be an option.
我最终手动转移了大约100个错误,因为我决定过多这些错误,并且值得花时间亲自查看每个错误并重新考虑优先级。如果你有更多的错误或没有在你的项目中的某个点退回并以这种方式查看整个待办事项列表是有意义的,这可能不是一个选项。
All that said: I'm loving FogBugz. The fact that our users and testers are getting confirmation emails with links to their tickets is forcing us devs to be more responsive to incoming requests, and the email tools make it easy to have a conversation about each issue. In my case, the import pain was worth it.
所有这一切:我很喜欢FogBugz。我们的用户和测试人员收到包含其门票链接的确认电子邮件这一事实迫使我们开发人员对传入的请求做出更快的响应,而电子邮件工具可以让您轻松就每个问题进行对话。就我而言,进口的痛苦是值得的。
#1
I tried it and it choked on our Wiki pages. I wasn't particuarly excited about the way the import tool mapped the Trac fields to the FogBugz fields.
我尝试了它,它在我们的维基页面上窒息。我对导入工具将Trac字段映射到FogBugz字段的方式感到特别兴奋。
Another issue is that you can't really delete issues once they're in FogBugz, so after the first failed import I just closed my Student & Startup account and opened a new one.
另一个问题是,一旦他们进入FogBugz就无法真正删除问题,因此在第一次失败导入后,我只关闭了我的学生和启动帐户并开了一个新帐户。
I ended up transferring our ~100 bugs manually because I decided too many of them were stale and it was worth the time it took to personally look at each one and rethink the priority. If you have more bugs or aren't at a point in your project where stepping back and looking at the whole To-Do list in that way would make sense, that might not be an option.
我最终手动转移了大约100个错误,因为我决定过多这些错误,并且值得花时间亲自查看每个错误并重新考虑优先级。如果你有更多的错误或没有在你的项目中的某个点退回并以这种方式查看整个待办事项列表是有意义的,这可能不是一个选项。
All that said: I'm loving FogBugz. The fact that our users and testers are getting confirmation emails with links to their tickets is forcing us devs to be more responsive to incoming requests, and the email tools make it easy to have a conversation about each issue. In my case, the import pain was worth it.
所有这一切:我很喜欢FogBugz。我们的用户和测试人员收到包含其门票链接的确认电子邮件这一事实迫使我们开发人员对传入的请求做出更快的响应,而电子邮件工具可以让您轻松就每个问题进行对话。就我而言,进口的痛苦是值得的。