Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2670

Support Manager: When searching tickets, search all replies and notes

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.2.0
    • Fix Version/s: 5.0.0-b1
    • Component/s: Plugins
    • Labels:
      None

      Description

      When selecting "Ticket Search" in the global search bar, it appears as if only ticket summaries are searched. It would be ideal if we could additionally search ticket replies and notes.

      Perhaps some benchmarking is in order to ensure it's not ridiculously slow, but the search isn't as effective as it could be without including ticket reply text.

      Originally requested here https://requests.blesta.com/topic/search-content-of-tickets

        Activity

        Hide
        jonathan Jonathan Reissmueller added a comment - - edited

        You want a dump of the support tables? I do

        Show
        jonathan Jonathan Reissmueller added a comment - - edited You want a dump of the support tables? I do
        Hide
        tyson Tyson Phillips (Inactive) added a comment -

        We can test it against your databases to start

        Show
        tyson Tyson Phillips (Inactive) added a comment - We can test it against your databases to start
        Hide
        tyson Tyson Phillips (Inactive) added a comment - - edited

        I updated this branch to search against a FULLTEXT index. This is much faster, hopefully you see a benefit too.

        For me, I have 200k replies with 80k tickets and the search page loads in 2.5 to 3 seconds.

        Also, I only have it searching replies, not replies/notes, nor all reply types since that requires an additional table join which adds another 1.5 seconds to page load time.

        I added the branch for v2.22.0 of the support manager (i.e. blesta v4.10+) because this migration takes a long time. About 35 seconds to create the fulltext index on those 200k records. This can pose a problem during upgrades (e.g. timeouts).

        Show
        tyson Tyson Phillips (Inactive) added a comment - - edited I updated this branch to search against a FULLTEXT index. This is much faster, hopefully you see a benefit too. For me, I have 200k replies with 80k tickets and the search page loads in 2.5 to 3 seconds. Also, I only have it searching replies, not replies/notes, nor all reply types since that requires an additional table join which adds another 1.5 seconds to page load time. I added the branch for v2.22.0 of the support manager (i.e. blesta v4.10+) because this migration takes a long time. About 35 seconds to create the fulltext index on those 200k records. This can pose a problem during upgrades (e.g. timeouts).
        Hide
        jonathan Jonathan Reissmueller added a comment -

        The fulltext index is supported in mysql 5.6+ and mariadb 10.0.5+ which are above the Blesta minimum requirements. We'll need to remove these changes and re-add them when we bump up the minimum requirements.

        Show
        jonathan Jonathan Reissmueller added a comment - The fulltext index is supported in mysql 5.6+ and mariadb 10.0.5+ which are above the Blesta minimum requirements. We'll need to remove these changes and re-add them when we bump up the minimum requirements.
        Hide
        abdy Abdy Franco added a comment -

        I think this issue should remain open, as it was postponed for a future version.

        Show
        abdy Abdy Franco added a comment - I think this issue should remain open, as it was postponed for a future version.

          People

          • Assignee:
            Unassigned
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              23/Dec/20

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day, 12 minutes
              1d 12m

                Agile