New Feature / Feature Enhancement

New Feature / Feature Enhancement

Submitted by (@simonegirlanda)

allow to add css or other html in Ticket::Frontend::ResponseForm

Allow the definition of a global answer template or to add css/html in the Ticket::Frontend::ResponseFormat configuration setting .

this template should wrap messages written by the agent (using a standard answer template or not).

allow the use of CSS / Styles in answer templates. Now they are removed from the HTML code.

Voting

2 votes

New Feature / Feature Enhancement

Submitted by (@matthias.terlinde)

Ticketlist as dashboard

Dear team, since idea nr. 420 (https://otrsteam.ideascale.com/a/dtd/Customer-Dashboard/116448-10369) hasn't any update since 7 years I dare to open this idea in addition. The standard ticketlist dashboards (e. g. escalated tickets, active process tickets, etc.) mostly don't fit all of the agent's needs. Making the ticketlists of the dashboardable is in my eyes a crucial and really helpful addition to the other dashboards. ...more »

Voting

1 vote

New Feature / Feature Enhancement

Submitted by (@oliver.schneider)

ressource calendar - same agent multiple teams not shown

We split our division into several teams of about 10-30 people inside there regular section. But of course they also appear in some kind of x-matrix teams as well as the section chiefs are in a ressource chiefs. If anybody adds an appointment, connected to a resource and agent, you cannot see it in other resources. The workaround is to mark all resources and then add the person. I see two problems with this solution: ...more »

Voting

0 votes

New Feature / Feature Enhancement

Submitted by (@lauffer)

SMIME and Tickets with lot of articles -> slow

If we open an ticket all articles were copied to the var/tmp/ directrory and if they have s/mime content they will be checked with openssl. This is a very, very time expensive task... check CRL lists...For example here we have a 30 article long ticket with round about 15 smime mails and opening the ticket (AgentTicketZoom) takes round about 11 seconds with s/mime. If we disable smime opening tackes round about one second. ...more »

Voting

0 votes

New Feature / Feature Enhancement

Submitted by (@cindy.fredriksson)

Customer object as a dynamic field in ITSM Changes

Currently the Customer object is not connected with ITSM Change, which hinders to have an overall look of all changes/work orders related to the customer. If it was possible to have a lock-up field for the Customer object, agents could easily choose an existing customer from the lock-up field in the ITSM Change. This prevents wrong spelling of the customer name in a customized text field. It also helps the Agents to get ...more »

Voting

6 votes

New Feature / Feature Enhancement

Submitted by (@otc.xunta.gal)

Restrict linked tickets shown at Config Item Zoom

In the Config Item zoom, there is no way to choose which linked items (for example: tickets) are shown, so, when too many tickets are linked to a CI, opening the CI zoom view could get slower, or simply not too smart when you need to scroll down for a long time. It would be great to make possible to configure from the SysConfig, which tickets and other elements are shown. It would be important to be able to filter archived ...more »

Voting

3 votes

New Feature / Feature Enhancement

Submitted by (@guenter.grein)

Configure ticket notifications per Queue

In heterogenious environments it would be helpful if ticket notifications could be configured per queue (similar to escalations) instead of configuring them globally. Some teams are working email focussed others are not. Some teams like to receive an email for every update of a ticket others want as few emails as possible. Ideally there could be a default configuration for all and a dedicated configuration per queue ...more »

Voting

-3 votes