Stefan Berder wrote:
Hi all, I'm now playing with otrs for a week and find this tool really handy. I used to work on RT (http://bestpractical.com/rt/) but it was hard to install, hard to configure, hard to modify, hard, hard, hard ... while with otrs, on eah thing I want to do I got an answer after looking in Kernel/Config/Default.pm or in the code. So thank you for this tool to the core team. Now for the questions : - Is otrs able to deal with actions in email subject ? My problem is that some agents prefer to handle the tickets without any web interface, so my point is to detect an answer of a ticket by mail and make it an agent answer, and for example other things like close for example. It could be detected by [close] in the subject or any other way.
Take a look at Chapter 7 in the documenation. Specifically you are interested in "Filtering/Dispatching by OTRS/PostMaster modules". http://doc.otrs.org/1.2/en/html/receiving-email-filter-module.html. Take a look at /opt/otrs/doc/X-OTRS-Headers.txt to see all of the default actions that can be performed with X-OTRS headers. If you need even more complex filtering, then you can write your own PostMaster filter modules. A brief introduction to them is here: http://doc.otrs.org/1.2/en/html/dev-custom-modules-postmaster.html. ** Filters are indescriminate. They do not do any kind of permissions checking before processing mail. Using filters to allow your agents to manage the system via email could be disasterous if end-users intentionally (or inadvertenly) place specific wordings in the subject or body that mimic agent actions.
- I don't really find the faq usage. The faq has to be filled as a separate section of the ticket system ? My point of view is that we
FAQ is considered a separate area of the system. It is not tied into or related to tickets.
should have the ability to fill it with tickets too, this would avoid to loose some time to fill it with an already solved problem.
Why? Now you have a duplicate copy of a ticket whose information could be just as easily accessed with the full text searching capabilities provided in the Utilities section. Personally, I dislike the idea of ticket dumps into FAQs. Agent writings inside of tickets are often sloppy and disjointed. The back and forth nature of tickets also makes for an often disjointed view of the problem and its solution. To dump this kind of information into an FAQ (especially if it is publicly viewable) is a poor idea (IMO). Rather I think an FAQ should be a well thought out, carefully constructed document that answers a question. Building this type of document generally is best achieved by creating it from scratch. Doing so requires thought. Dumping tickets requires none. Just my $.02.
- Is there any guy who is about to provide a debian packaging of this wonderful application ? If no, I'll probably do it.
Look here: http://lists.otrs.org/pipermail/otrs/2004-April/004692.html
Thanks to those who will answer
Stefan