Disabling Frontend::RichText may be necassary if local security policies may not allow to send html mails. But a disabled Frontend::RichText affects the FAQ module, too. And it makes no sense to have non html faq web articles. So either you need to hack otrs and disable richtext in the email compose module or you need to hack the faq to enable RichText. It is a very, very simple task to patch OTRS to do that. But it ...more »
It should be possible for the user to proactively highlight text to be quoted in replies. Currently there is only a system-wide setting. Allowing the user to highlight text, then choose reply adding only the selected text to the new reply would be much more efficient. Selecting multiple passages in the text would create two quote blocks. The OMQ plugin does this.
Innerhalb von OTRS sollte es ein Forum geben. Kunden sollten über den OTRS Login miteinander interagieren können.
There should be a forum within OTRS. Customers should be able to interact via the OTRS login.
Dear Sir or Madam, Is it possible to create "temporary stored Fields" (for example an Emergency Telephone Number to reach the customer). Most of the time it is required to store Personal Information for a concrete business concern (which is possible in GDPR). But the option to "Forget" must be implemented. Therefore a deletion after ticket Close would be a nice Feature. If there are fields especially for that purpose, ...more »
This function may include the creation of new contracts with a customer associated, beginning date and end date, scope, attachments, etc, date of maintenance programed. When those date are close to be up create tickets automatically and notification. When you are trying to create a ticket it validates if the client has contract or not (validating trough the dates).
we have a knowledge base process in OTRS. Unfortunately there's no Operation FAQ::FAQCreate available, so we've to create the new FAQ article manually. To improve the usability of OTRS and the FAQ module, a new GI Operation should be available (e.g.: FAQ::FAQCreate)
Display DynamicFields according to its type. Example: Textarea content is usually more text and should not be shown only in the small ticket information column but e.g. in an own widget in ticket zoom.
We want to be able to book appointments in a team calendar with a variable number of team members. This team calendar should indicate when the maximum amount of available resources (team members) is reached in a same time frame and prevent adding an event in this case. Hence, supposing we have a team calendar composed of 4 agents, it shouldn't be possible to create a fifth event say today between 10:00AM and 11:00AM if ...more »
Do not let every agent in the system see the full list of customer users. You can block access to the customer information center, but the agent will still be able to see every customer in the To: field with auto complete e.g. when writing a new ticket.
It's in business solution, i know.
In the customer information center OTRS displays a list of Customer Users assigned to a certain customer company. The displayed attributes of the Customer Users list cannot be modified. It would perfect if these attributes could be modified on a per agent setting or at least in a global definition.
A new screen on Customer Interface to show unanswered surveys.
The customer clicks on one unanswered survey and is redirected to it.