-
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-12-26] [$500] Web - Chat - Workspace avatar is greyed out in the conversation report preview #32984
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Triggered auto assignment to @NikkiWines ( |
@kbecciv Can you confirm this problem with new workspace? |
ProposalProblemChat - Workspace avatar is greyed out in the conversation report preview Root CauseIn Changeswe should check if avatar is not empty and if it is we should fallback to default workspace avatar. const avatar = allPolicies?.[`policy_${report?.policyID}`]?.avatar
return avatar ? avatar : getDefaultWorkspaceAvatar(workspaceName); |
Confirmed this isn't happening on prod, and is happening on staging and dev. It's occurring even if the backend is pointed to the commit before the merge commit for https://github.com/Expensify/Web-Expensify/pull/40008 so not tied to the backend PR that was tagged. It looks like it's most likely the result of #32546 cc: @mountiny @kubabutkiewicz @shubham1206agra The simplest solution to this is just to use Edit: Based on the linter failing, seems like we might not allow |
Yep, I'll apply your solution to my PR @ishpaul777 and you can be compensated for providing a valid solution here |
Triggered auto assignment to @laurenreidexpensify ( |
@laurenreidexpensify can we issue payment to @ishpaul777 for providing the solution to this deploy blocker please |
Will do, following the process where this is on prod for 7 days |
Current assignee @laurenreidexpensify is eligible for the Bug assigner, not assigning anyone new. |
Bug0 Triage Checklist (Main S/O)
|
@ishpaul777 pls apply to the job in Upwork thanks upwork.com/jobs/~014d0b71872c14469e |
Since it was internal person applying the fix and not the contributor we usually go with 25% of the original reward so that would be $125 to @ishpaul777 |
Reproduced on latest PR reviewed & approved. |
This is showing on the latest checklist as I didn't remove the label. This is now resolved and awaiting payment. |
Prod for 7 days will be Dec 21st |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.13-8 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-12-26. 🎊 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.
For reference, here are some details about the assignees on this 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:
|
Issue is ready for payment but no BZ is assigned. @bfitzexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
|
Offer sent @ishpaul777 |
Also, @ishpaul777 can you please complete the checklist in #32984 (comment)? Thanks! |
Actually I dont have access to guidelines to complete checklist items thats basically what C+ does on normal issues, but from my experience with similar issues i think this was minor syntax mistake in code that cause the bug so no regression test requires.. |
Cool, that seems fair to me. OK, let's close this one out then. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.12.0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
Workspace avatar is visible in the conversation report preview
Actual Result:
Workspace avatar is greyed out in the conversation report preview
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6311868_1702483241237.workspace_avatar_is_greyed_out.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: