I wonder whether it would be helpful to integrate a negative search (eg. all tickets w/o a keyword)?
I suggest to enable the CI search during ticket creation and ticket work to display Class dependent CI search attributes - like in the Config Item search module.
On the Search page it is possible to search for tickets changed during a certain period. It would be helpful if it was also possible to invert the search and search for tickets NOT changed. This would be a helpful option for supervisors / managers to monitor their staff and to make sure to tickets get 'forgotten'.
And as Nils, etc below said, in fact most search options would benefit from a 'not' function.
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.
I'd like to see a feature for searching on a company name (the name column in the customer_company table) from the search dialog box.
in order to make agent life easier it would be great to have some overview of "my last" performed actions / tickets in otrs. For example:
- chronological list of my last commented tickets
- chronological list of my last answered tickets
- chronological list of my last closed tickets
- chronological list of my last moved tickets
It would be nice to have faster serach engine in OTRS 3.
I think it must be any popular "full text serach" indexer, but not MyISAM in mysql of course !
I would like to developing this idea from concepts to OTRS 3 independent package but I need recomendations / opinions / suggestions.
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.
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).
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.
I suggest that clicking on the title of any dashboard dashlet should run the same search criteria, but with no limit on the results returned (dashlet default is usually 10), and that these results should be displayed using the usual ticket search results output.
Make a search function in the AgentTicketMerge View (same like AgentLinkObject View). So its easier to find the tickets you want to merge ...
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.
Allow generic agent to search for multiple variables in the same field (based on OTRS 2.4.5) using a special separator and have a copy paste generic agent job.