I too noticed this, Wes.  Was curious if this was by design as well.  The "Subject Line" search was extremely useful to us.  Didn't see anything in release notes indicating this feature had been removed.

Hi Wes,

 

This is by design and will be included in the release notes for the minor version. The Search String field already searches the ticket body, subject and notes so having a Subject field was a little redundant. If you move your search to the Search String field, however, you should still find the ticket in your results.

 

I would disagree, Andrea. The search string feature of advance search returns too many results to be accurate, if any at all. The subject line search was much more accurate. For example, if users include a customer order number in each email subject line. The user can easily search the subject line field and return a couple results, where as the search string field would return many results, some times none at all.

 

While the programmers may have found it redundant, it was not hurting anything and was actually quite useful, so why remove it? How can this feature be reintroduced or how can the search string field be more accurate?

 

 

 

 

Hi Andrea,

 

Thank you for the replying to this thread. 

 

Using "Search String" provides far too many results when searching for a specific ticket. 

 

You'd indicated in your reply that using the "Search String" field "searches the ticket body, subject, and notes."  It would seem that by design this is more taxing on the server rather than searching one specific field.   By that rationale, why not remove all other search fields aside from "Search String" ?

 

Perhaps one field with a dropdown box could resolve this?  The drop down could include Ticket Number, Search String, E-mail Address. etc.

 

The removal of this feature makes it much more difficult for us to locate specific tickets. 

 

Thank you again for your response and for taking this feedback into account.

This is an issue for us too - the Search String search produces far too many results whereas the Subject line allowed for more narrow and therefore more accurate results.  Please restore it!

Not only an issue with providing way too many results. It's taxing the server. Notes, Description and Subject fields for thousands of tickets? We generate 12 to 15k calls a month for just one brand.

 

A lot of times people are just giving up waiting for it to give results back and cancel.

 

Can this be put back the way it was? Until SmarterTrack does a overhaul of it's very limited search system, you shouldn't be combining so many fields together. It gives terrible, unreliable results, and is very heavy on server resources for what seems to be very little if any gain.

 

 

 

 

I'd just like to state that I restored the subject functionality to my version of SmarterTrack by copying all files EXCEPT frmTicket.aspx from /Management/Tickets directory from 10.2.5364 over to my version (10.4.5448). 

 

For some reason, copying over frmTicket.aspx from 10.2.5364 broke the transfer button.

Thank you all for your feedback. I've brought your concerns to the development team, and they are discussing a solution for a future version. One note that may provide some reassurance - When doing a search using the Search String field, the subject text is weighted much higher than others. So while there's not a Subject field, the results with a matching subject should appear higher on the list of results.

 

Thanks!

Hello all,

 

Thank you for your discussion on this thread. We appreciate the user input.

 

After extensive internal discussions, including discussions stemmed from input from the user community, we've added an alternative solution for the advanced search by subject. Information on this can be found below, as well as in the 10.x Release Notes for version 10.6.5549:

 

Please understand that we realize there is still functionality you'd like to see available. We're discussing improvements that can be made and are working to continue making it better for you. 

 

Thank you,

Hi all,

 

I know this thread has been marked as completed and the subject line search has been added back to SmarterTrack, but I'd just like to let you all know that there is another thread available for discussing SmarterTrack's search functionality. We'd like to centralize the conversation in order to prep for the next major version of SmarterTrack. Please reference this thread for continuing SmarterTrack's search discussion or to offer your input: http://portal.smartertools.com/community/a86741/discussion-smartertracks-search-functionality.aspx

 

Thank you! 
 

We have found the Search String field is very useful searching for our tickets because it searches in the body, subject and notes, however the aggravating and unorganized part of that feature is not being able to organize the results at least by date(started - that’s the main one we need to organize with)... it would be nice if we could organize by columns up top such as by date (started column), status, and idle time, the others up top would be nice too but the ones we would search by for sure would be date (started column), status, and idle time. I want to see the oldest to newest tickets a customer may have. Yes the advanced search with specific custom fields lets you organize by date, but our issue is if the variable wasn't added to the custom field in the ticket in the first place, or if it’s a ticket that does not use that custom field the ticket will not show in our search results so we do not see all tickets associated with cx name "x" for example. To ensure a ticket is not missed in the lineup being able to organize the search string results by date(started)  is imperative for us.