You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2020. It is now read-only.
Describe the bug
The participation of a member can be counted multiple times and
a member can be counted present even after the meeting has ended.
To Reproduce
Steps to reproduce the multiple count:
Click on the notification slacks sends you multiple time
Steps to reproduce the participation after the meeting has ended
Click on the notification to join the meeting after 30min
Expected behavior
If a member has already participated in a meeting we should not double count their presence but still redirect them to the meeting URL.
If a member tries to join after 15 min (I think we have field for this in our DB) they should not be counted as present but still get redirected to the meeting
Additional context
We should be careful about the fire_date. I am not sure which timezone the fire_date field is in.
The text was updated successfully, but these errors were encountered:
Describe the bug
The participation of a member can be counted multiple times and
a member can be counted present even after the meeting has ended.
To Reproduce
Steps to reproduce the multiple count:
Steps to reproduce the participation after the meeting has ended
Expected behavior
If a member has already participated in a meeting we should not double count their presence but still redirect them to the meeting URL.
If a member tries to join after 15 min (I think we have field for this in our DB) they should not be counted as present but still get redirected to the meeting
Additional context
We should be careful about the
fire_date
. I am not sure which timezone thefire_date
field is in.The text was updated successfully, but these errors were encountered: