• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Customer Portal
    • 4
    • 14
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      At the moment, we have the following condition on how the Smart Search works in the Customer Portal for the Request Type:

      • The primary search picks up words that the customer is typing in the Summary field, and looks for them in the request type's Name and Description.
      • The secondary search uses JQL queries to find relevant request types based on the request's Summary field.

      The above is taken from "How the search works". But, it appears that the ordering has its own rule where it will order from the newest to the oldest. For example:

      Even though "Hardware Fault" at the bottom match the name and description, as it is the oldest request type that is created, it is put at the bottom of the list. This can result in an unwanted list of request types from the search due to those mentioned request type has the same string in its description.

      Suggested Solution

      To have an option to control how the Smart Search in the Customer Portal works, such as;

      • Prioritise Request Type Name
      • Need to match both Request Type Name and Description.
      • Match either the Request Type Name or Description (Default)
      • Prioritise Request Type Description.

          Form Name

            [JSDSERVER-6578] Smart Search Configuration

            SET Analytics Bot made changes -
            Support reference count New: 14
            SET Analytics Bot made changes -
            UIS Original: 3 New: 4

            It would be nice is the primary search was off of the request name and then the other smart features like ticket summaries on those request types. It seems like Request Types won't even show up if they don't explicitly type the full name of the type. Plus if you have 3 request types with very similar names such as "Enterprise Linux", "Reliability Linux", and "Market Linux", the search will only show 2 of the 3 if a user searches for "Linux".

            Luke Miranda added a comment - It would be nice is the primary search was off of the request name and then the other smart features like ticket summaries on those request types. It seems like Request Types won't even show up if they don't explicitly type the full name of the type. Plus if you have 3 request types with very similar names such as "Enterprise Linux", "Reliability Linux", and "Market Linux", the search will only show 2 of the 3 if a user searches for "Linux".
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3
            Marc Dacanay made changes -
            Labels New: ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 976866 ]
            SET Analytics Bot made changes -
            UIS Original: 3 New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3
            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 1

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Votes:
              14 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: