Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pop a toast when a participant tries to move ahead of the meeting facilitator #576

Closed
jordanh opened this issue Dec 15, 2016 · 3 comments
Closed

Comments

@jordanh
Copy link
Contributor

jordanh commented Dec 15, 2016

Issue - Enhancement

When a meeting participant tries to navigate ahead of the facilitator, presently the click falls into a void. For example, when a participant tries to click on an agenda item while the facilitator is still in Project Updates. It can sometimes feel like our app is broken.

I suggest we pop a toast when this happens to that participant that reads:

Hold your horses! 🐴
You'll have to wait for the facilitator
before you can go there.

@jordanh
Copy link
Contributor Author

jordanh commented Dec 15, 2016

This issue is available under our Equity for Effort program. Comment below if you'd like to take it on!

@jordanh jordanh changed the title Pop a toast when a participant tries to move ahead of the 'tater Pop a toast when a participant tries to move ahead of the meeting facilitator Dec 15, 2016
@jordanh jordanh added this to the Epic 2: Beta milestone Dec 20, 2016
@jordanh
Copy link
Contributor Author

jordanh commented Dec 20, 2016

This popped up in #578.

Here's what I think happened:

  1. The facilitator started the meeting but never ended it
  2. A second user logged in to try and use Action (probably to use the team dashboard) and they see that a meeting is active
  3. They join the meeting with the intention of ending it but they can't (without knowing the secret incantation)
  4. Most importantly, the user didn't even realize they were not the facilitator - it just look like our software was stuck

Super frustrating!

In addition to this bug, what to do? Brainstorming options (in addition to the above):

  1. If a meeting has been active for >24 hours, end it automatically (requiring a server task)
  2. Add a button to the team dashboard modal offering to end a meeting if it has been active for > 24 hours
  3. Add a button to the meeting sidebar for the same
  4. Other?

I'll open a separate issue to track.

@jordanh
Copy link
Contributor Author

jordanh commented Jan 11, 2017

Closing in favor of solution from #592

@jordanh jordanh closed this as completed Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant