-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
4.4
-
MOODLE_404_STABLE
When users participate in a BBB meeting within Moodle, their entry into the meeting is correctly logged in the Moodle logs. But if a user leaves the meeting "abruptly", i.e. without using the Leave meeting button (e.g., by closing their browser window or tab), this action is not recorded in the Moodle logs.
However, in the Timeline component of the Learning Analytics Dashboard, it is shown correctly when a user has left, even if it was without using the Leave button, meaning BBB does detect their absence. So one could expect to find this critical information is the Moodle logs.
Steps to Reproduce:
- Join a BBB meeting via Moodle as a moderator.
- Join with another user to the same meeting (e.g., in another browser).
- After a half a minute or so*, exit with the second user by closing the browser window or tab (without using the built-in "Leave meeting" functionality).
- As the moderator, open the Learning Analytics Dashboard. The other user will appear as offline, and the Timeline will show the interval when the second user was online.
- Check the Moodle logs for any entry indicating the second user leaving the meeting. You should find none
- the waiting time has no effect on the issue, it's just easier to see the user's presence on the timeline after waiting a bit
Expected Behaviour: An entry should be created in the Moodle logs indicating that the user has left the BBB meeting, regardless of whether they used the "Leave" functionality or simply closed the browser window or tab.
Actual Behaviour: No log entry is created in the Moodle logs when a user leaves the BBB meeting by closing the browser window or tab. Only entries for joining the meeting are logged, and when the Leave meeting button is used.
As the data shown on the Analytics Dashboard is accessible only during the meetings and shortly after, then it is lost, having at least the joining and leaving times in the Moodle log would be a great help (e.g. if moderators forget to download the session data).