-
Notifications
You must be signed in to change notification settings - Fork 336
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
Meeting Stuck at First Call #578
Comments
Oh, so whack! Did you show them the super secret key sequence? |
I didn't want to whack it yet. I wanted to preserve the state so we could see what might be wrong first... ;) |
Yeah, I thought you might be thinking that!! |
investigating now... |
Unable to reproduce. Here are the steps I took:
|
state:
|
@mattkrick I deployed the new user impersonation feature up to staging. Check it out!
Fun! |
Very cool! Guess we should probably remove |
Good good thoughts Matt: it should already be done on production!
|
@jordanh have you been able to reproduce? |
Yes, but only switching to Clay's account. Try it on staging. It's neat. If you want to look together, ping me! |
Ah ha! It was as I suspected. Clay is not the facilitator. His colleague Alix is. That means he can't go forward, and he can't end the meeting. Super frustrating! This makes #576 more important. Let's continue the conversation there. |
Issue - Bug
Clay Parker Jones at August showed me today that they have a team that is in a stuck meeting state. They are unable to advance beyond the First Call phase.
Steps (for him):
They can add agenda items, but he is unable to navigate.
No exceptions are triggered.d
The text was updated successfully, but these errors were encountered: