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

[BUDI-7085] Multiple dev collab: User has to refresh when the last user leaves the app to get design/automation access #10785

Closed
1 task
shogunpurple opened this issue Jun 5, 2023 · 1 comment
Labels
avalanche OSS team bug Something isn't working sev1 - critical Severity Level 1 Bug - Critical path loss of functionality

Comments

@shogunpurple
Copy link
Member

Checklist

  • I have searched budibase discussions and github issues to check if my issue already exists

Hosting

  • Cloud - qa env
    • Tenant ID: martin

Describe the bug
When a user is collaborating with another in the data section, and the user that currently has design/automation privilege leaves, the other user has to refresh to get access to design/automation.

To Reproduce
Steps to reproduce the behavior:

  1. Log in with 2 accounts and access the same app
  2. Leave the app with the first account
  3. The other user is the only user in the "room" but needs to refresh to get the design/automation access

Expected behavior
Should update automatically through the websocket when the first user leaves the room.

Screenshots
https://jam.dev/c/39010384-1309-4dc8-a523-e5f0bbc712ab

App Export
N/A

Desktop (please complete the following information):

  • OS: OSX Ventura 13.0.1
  • Browser Chrome
  • Version 113.0.5672.126 (Official Build) (arm64)

Additional context
Add any other context about the problem here.

From SyncLinear.com | BUDI-7085

@shogunpurple shogunpurple added avalanche OSS team bug Something isn't working sev1 - critical Severity Level 1 Bug - Critical path loss of functionality labels Jun 5, 2023
@aptkingston
Copy link
Member

Closing as dupe of #10786.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
avalanche OSS team bug Something isn't working sev1 - critical Severity Level 1 Bug - Critical path loss of functionality
Projects
None yet
Development

No branches or pull requests

2 participants