Wir möchten die Volltextsuche als kleines Eingabefenster in der Titelleiste zurück, wie bei Version 5 und 6. Die zwei neuen kleinen Fenster für CustomerID und CustomerName sind nutzlos, wenn man zB eine Ticketnummer suchen möchte oder Volltext und die Elasticsearch bringt nicht die Ergebnisse die man braucht. Wir möchten daher das Fensterchen aus Version 5 und 6 zurück. Es wäre auch ok, wenn man die zwei kleinen Fenster... more »
With integrating ElasticSearch in OTRS 7 the input-field for FulltextSearch disappeared in the main menu. Suggestion for OTRS 8 Agent-Frontend: It should be possible for agents to search a ticket by ticketnumber without opening another window (like still existing search for customer / customer-user). Maybe other companys are focused on different search-attributes. So it would be great to select in sysconfig the search-attributes... more »
It would be great if OTRS Reports Module could generate "Dynamic List" kind reports. Today it is not possible.
Another alternative way to get lists of CIs is that the Search functionality in the CMDB could use a Multiple Selection Field, to be able to perform searches over several CI classes at once.
If you want to link a config item to a ticket from inside the ticket you can only search for it by - ConfigItem# - Name - Deployment State - Incident State (see CISearchFromTicket.png) It would be nice if you were given the same choice of custom fields just like when searching the CMDB (see CISearchFromCMDB.png). Because right now we always have to open a new tab, search for the CI there and copy over the CI#... more »
It should be possible that if you add text to title or body to a new ticket - or if you work as an agent on an existing ticket - there should be related tickets proposed. This might work similar to the FAQ-feature in the customer portal. So maybe the text is checked automatically for key words and somewhere there is a box where there are tickets shown which contain the same key words (which are found there automatically... more »
Search Results as Dashlets It would be a great (and preferrably easy to implement) idea to be able to make saved searches available in dashboards. So that if you define a search and save the parameters you could choose this saved search to appear as a dashlet in the dashboard. Seems to be pretty easy and would offer a lot of useful things (e. g. keeping track in the dashboard of all tickets in a certain queue which have... more »
Allow searches in Sysconfig to find Dynamic Field Names. I am getting ready to add a dynamic field to production that I added to my test site many months ago. I don't remember all of the forms that I added it to. It would be great if I could search for the dynamic field name to find where it is used.
We need to look for tickets by number a lot. Search field
is good, but full text search takes a lot of time.
And a switch that says that we are looking for a ticket number, or a separate search field like
could be a great thing.
When searching a CI, i wish there would be a possibility to search in all classes (by name).
But you have to select a class first, bevore searching.
It would be nice to select 'all' and then search by name in all classes.
Or by all configured fields (must be in all classes).
It would be usefull, if you can search for a involved agent in the tickets. The mask for search should have a field "involved agent" additional to owner.
Allow multiple selects with option to zoom each ticked/checked case to open in a new browser tab vs. one off case tick/check and zoom to new browser tab. Could also include the other functions such as unlock/lock, history, priority, note, close, and move. When you select bulk tick/check box it does not provide any fo these options.
Two improvements to agent searching options: -#1 Currently stringing multiple fields together assumes an "and" relationship between the fields. (i.e. ticket was created today AND responsible is me). I would like to have the ability to have an OR relationship between search fields (i.e. Customer is X or Responsible is Y). -#2 Provide the ability to search on tickets based on article level details (i.e. display all... more »
When you want to select an agent to be informed optional by a note, set as owner or responsible you can type the first letter on the keyboard to jump to the agents starting with this letter. Unfortunately this is only working with the first letter. I do suggest to have this feature implemented as an instant search, so when you type the first few letters of an agent name you will jump directly to that agent.
I suggest you to extend the search of extisting Users to be searchable in the email of the user too.
The Advanced Search window has a lot of information in a small space. I think it would be a good idea to add to horizontal lines to separate the Template related items at the top and the field selection related items at the bottom from the filtered fields in the middle. Or put a box around each of the 3 sections.