There are several key things that all our teams do in all our OTRS systems: Open, Answer and Close Tickets Assign Tickets to People and Queues Delete Tickets, and finally MERGE Tickets As we use the email-to-OTRS mechanism for ticket creation quite heavily, merging tickets is probably about the 4 or 5 most common task our teams perform to properly organize support issues. Unfortunately, merging ticket is also, bar none ...more »
Some customers want to see their company tickets after they login and some customer their own tickets. It would be great if a customer could define the default view after a login in his preferences.
I suggest to keep the main menu bar (showing Dashboard, Ticket, Faq, Statsitic, ...) at fix position on the screen, so that it even remains visible if you scroll down the page (Similar like it is implemented in ideascale or similar like you can fix view on certain cells in MS-Excel).
I suggest to change the layout of the "Change Agent Relations for Role XYZ" page. Currently there is a long list of all agents and a tick for the agent of the role XYZ. Especially when you have lot of agents it is difficult to have a quick overview which agents do have a tick for role XYZ. I suggest to have a "two row" view: On the left you have a list of all agents and on the right you have a list of all agents of the ...more »
I suggest a headline for the search result view.
If an agent search for tickets, with a template configured or with parameters set, the search result do not show a headline to identify the search process.
The headline could show the name of the search template or a truncated set of parameters set.
I suggest to have two different views of ticket view. One view as it is, meaning article sorted by date and time. And another view where you can see nested articles, as known from discussion forums. When viewing a dedicated article you should have the option to comment directly on this article and then the new created article (your comment) should be added directly under the previous article - so it is very easy to follow ...more »
I think it's very useful to see a tree view of the queue, being able to browse the ticket inside of each queue and sub queue.
Queueview in OTRS allows you to see the ticket in the queue, but only of those unlocked.
Make a search function in the AgentTicketMerge View (same like AgentLinkObject View). So its easier to find the tickets you want to merge ...
I would like to have a new setting for Agent preferences, that will allow to select the initial view after logging in to OTRS: - Dashboard (current default, if dashboard is active), - Queue view - Status view - Escalation view - (some other view?) Some agents prefer to go to Dashboard initially, others would like to be in Queue view by default. I know that I could do that by providing adapted URLs as favorites to agent ...more »
It's great to have a notification by a ticket to tell me that it has one or more unread articles but (IMO) a huge omission not to allow me to sort by this value. When help desk staff are looking at which unlocked tickets in their queue they should be prioritising, it's surely the ones with an answer from the customer that are the most important. I was hoping to create a new dashlet that would list tickets first by new ...more »
I suggest to improve the way classes and sub-classes are shown on AgentITSMConfigItem, and make them look like queues and sub-queues are shown. When building a large CMDB, it's neccesary to create sub-classes inside classes. Since OTRS creates sub-queues and sub-services on database using the parent::child syntax, it's easy to think this is the way sub-classes on CIs should be created so we have a Servers class and then ...more »