-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Web-Workspace -After renamed the workspace, you need to refresh the page to see the new name #12000
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @ctkochan22 ( |
This is reproducible on prod. Not a deploy blocker |
We used Deploy Blocker label, because we can not reproduce it in production |
Oh let me try again to make sure. Edit: I'm more than confident its happening with the Concierge message. |
Issue not reproducible during KI retests. (First week) |
This only happens if they change the name before you get an automatic message about guides |
@ctkochan22 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Still happening. I think this is internal, need to test what keys are being updated when the message about the guidse comes though |
I'm going to make this monthly while it's on HOLD. |
Issue not reproducible during KI retests. (Fourth week). Can we close this as its not repro? |
@neil-marcellini What do you think? Given that QA isn't able to reproduce this any long I'm inclined to close, or we need to update the reproduction steps so it's more clear how Applause can get the same result. |
I tested on staging and it looks like it's no longer reproducible while online, which is kind of odd. I'm not sure how it was fixed but that's good. However the issue is still reproducible when the workspace is created and renamed while offline. I will update the description. |
Thanks! I'll also take this over as part of the broader tracking initiative. Feel free to assign yourself to #12775 as well. |
Still holding and not a priority. |
Still far from being a priority. |
We are still holding this on #12775. I'm suggesting that we start working on that issue again. |
Awesome that sounds great! |
Holding, we have a potential solution for #12775. |
Still holding, see the updates in the replay effect issue. |
Fixed! Screen.Recording.2023-05-16.at.8.54.42.AM.mov |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Log in with any account
Go offline
Create a new worksapce
Rename the workspace Workspace
Go back to the settings and go back online
Expected Result:
The workspace remains renamed
Actual Result:
The workspace is reverted to the initial name until you refresh.
Workaround:
Refresh.
Platform:
Where is this issue occurring?
Version Number: 1.2.18.2
Reproducible in staging?: Yes
Reproducible in production?: No
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.2022-11-28.at.9.06.06.AM.mov
Out-dated video when the bug occurred while online.
https://user-images.githubusercontent.com/93399543/196772472-9c6035bd-2064-46d9-a847-9149a55f623c.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: