Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-60039

Messaging search areas use timecreated instead of timeread to index search

XMLWordPrintable

    • MOODLE_32_STABLE
    • MOODLE_32_STABLE, MOODLE_33_STABLE
    • MDL-60039_master
    • Hide
      1. Enable global search and configure it
      2. Have 2 users enrolled as students in same course.
      3. Send message from user 1 to user 2 with content 'balloon'.
      4. As admin, run the global search indexing scheduled task via the UI
      5. Log in as user 2 and click the bubble notification in the top right. Message should now be read.
      6. As admin, run the global search indexing scheduled task via the UI
      7. As user 1, search for 'balloon', a result should be returned
      8. As user 2, search for 'balloon', a result should be returned
      Show
      Enable global search and configure it Have 2 users enrolled as students in same course. Send message from user 1 to user 2 with content 'balloon'. As admin, run the global search indexing scheduled task via the UI Log in as user 2 and click the bubble notification in the top right. Message should now be read. As admin, run the global search indexing scheduled task via the UI As user 1, search for 'balloon', a result should be returned As user 2, search for 'balloon', a result should be returned

      Messaging search areas only index read messages, they should be indexed using the timeread value, not timecreated, because timecreated is the time the message was created and some messages will not be indexed as expected.

            dmonllao David Monllaó
            dmonllao David Monllaó
            Mark Nelson Mark Nelson
            Dan Poltawski Dan Poltawski
            Ankit Agarwal Ankit Agarwal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.