-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[HOLD for payment 2023-02-08] Chat - Concierge chat links opening in OldDot #12594
Comments
Triggered auto assignment to @muttmuure ( |
@kbecciv I'm not sure I know what 1. Create a brand new account means - do you mean a unique domain? |
@muttmuure No, you can create regular public account. |
@kbecciv Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@muttmuure Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I can't reproduce: 2022-11-22_14-02-44.mp4 |
Please feel free to reassign or clarify the exact steps! |
@kbecciv if you sign in with the Olddot sign in portal afterwards it actually navigates you to NewDot: not.a.bug.movClosing |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.63-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-02-08. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
bump! also assign a bz here! |
@muttmuure Assigning you since you were the original BZ member on this (I believe) |
Assigning @Santhosh-Sellavel since he was the C+ member who helped me debug and review my PR! |
I didn't realize this was reproducible and fixed. I'll issue payment this week |
@muttmuure payment It's due last week. |
Upwork is showing an error when I try to create a job for payment:
Going to try again later. |
Still seeing the error message. Posted about it here: https://expensify.slack.com/archives/C01SKUP7QR0/p1676543857805809 |
@Santhosh-Sellavel the job listing is here: https://www.upwork.com/jobs/~01dd7b52b0c3b37962 |
Thanks applied now! |
Rehired - when you've accepted I can get you paid + bonus |
Accepted @muttmuure, not sure why bonus here? |
@jasperhuangg, @muttmuure, @Santhosh-Sellavel Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Oh yes - you're right. I typically review for bonuses when I'm paying. This has been paid so we're all set. Thanks @Santhosh-Sellavel! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Issue found when executing PR #12376
Action Performed:
Expected Result:
Verify that the #admin room is opened in the same tab
Actual Result:
Taking user to OldDot
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.25.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug5813649_12376.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: