6 Jul 2006 10:40
Feature-requests for OTRS
Alexander Scholler <alexander.scholler <at> augsburg.de>
2006-07-06 08:40:37 GMT
2006-07-06 08:40:37 GMT
Hi Dev-Team, JFYI... I collected some, I think useful feature request including motivation for further OTRS versions. Of course the use of these features should not be obligatory, but I think theses features could be a good enrichment of OTRS capabilities. 1a) Ability to edit article type (not necessarily content) after creation. Why? Some informations are not for the eyes of the customers 1b) Mail-replies (follow-ups) not coming from the mail-address of the current customer should be of type internal. Why? Otherwise possibly existing internal informations within the reply could be read by the customer. 2) Additional ticket-property: customer-supervisor beside the customer. Why: Some companies have 1st level support within the customer-teams or the OTRS-team give support for customer-companies. Each person within these companies can contact the OTRS-team, but a special person within the customer-company should be informed about this contact. This is already realized within the customer-webgui with "company-tickets". A corresponding solution within the mail-response-agent-gui would be that if a agent composes a mail-response, all customers which can view this ticket within their "company-tickets" are shown as possible mail-cc-recipient which only have to be checked to receive a copy of the mail. 3) Additional ITIL-specific ticket-properies like ticket-classification(Continue reading)
, has
this maybe been already implemented by anyone? If not, is there any
technical aspect that speaks against this solution?
Upon a first glance, I'd try to implement this within System/Email.pm.
At that point, is it possible to get the ticket object for which an
email is being sent?
Regards,
Wolf
RSS Feed