I was researching this a while back when we were considering replacing our helpdesk software. We ended up keeping our current product, as the cost of retraining and re-doing all the integration points for a new package was too high. Assuming you don't have these issues, this is a good place to start: http://www.opensourcehelpdesklist.com/
You can try with BugTracker.NET it is open source and have e mail integration, also great thing that it have API for adding new BUGs using http requests, so scripting old e mails should not be so hard
In the end I used OTRS and I found it to be SO good that I didn't need much customization. The small changes to the code that I needed I directly did them in Perl even if I didn't know this language before, and considering the quality of the software it is well worth the effort. I definitely recommend it.
发布评论
评论（3）
不久前，当我们考虑更换我们的帮助台软件时，我正在研究这个问题。我们最终保留了当前的产品，因为重新培训和重新执行新软件包的所有集成点的成本太高。假设您没有这些问题，这是一个很好的起点：http://www.opensourcehelpdesklist.com/< /a>
I was researching this a while back when we were considering replacing our helpdesk software. We ended up keeping our current product, as the cost of retraining and re-doing all the integration points for a new package was too high. Assuming you don't have these issues, this is a good place to start: http://www.opensourcehelpdesklist.com/
您可以尝试使用 BugTracker.NET 它是开源的并且具有电子邮件集成，这也是一件很棒的事情具有用于使用http请求添加新BUG的API，因此不应编写旧电子邮件的脚本太难了
You can try with BugTracker.NET it is open source and have e mail integration, also great thing that it have API for adding new BUGs using http requests, so scripting old e mails should not be so hard
最后我使用了 OTRS，我发现它非常好，我不需要太多定制。即使我以前不了解这种语言，我也直接用 Perl 对代码进行了一些小的修改，考虑到软件的质量，这是非常值得的。我绝对推荐它。
In the end I used OTRS and I found it to be SO good that I didn't need much customization. The small changes to the code that I needed I directly did them in Perl even if I didn't know this language before, and considering the quality of the software it is well worth the effort. I definitely recommend it.