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

[HOLD for payment 2023-12-26] [$500] Web - Chat - Workspace avatar is greyed out in the conversation report preview #32984

Closed
1 of 6 tasks
kbecciv opened this issue Dec 13, 2023 · 27 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor

Comments

@kbecciv
Copy link

kbecciv commented Dec 13, 2023

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:

  1. Create a NewDot workspace if you don't already have one.
  2. Open the workspace chat for your workspace.
  3. Press the +, Request Money, then Distance and complete a distance request.

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?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

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
  • Upwork Job URL: https://www.upwork.com/jobs/~014d0b71872c14469e
  • Upwork Job ID: 1735260103087415296
  • Last Price Increase: 2023-12-14
@kbecciv kbecciv added the DeployBlockerCash This issue or pull request should block deployment label Dec 13, 2023
Copy link
Contributor

👋 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:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

Copy link

melvin-bot bot commented Dec 13, 2023

Triggered auto assignment to @NikkiWines (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@shubham1206agra
Copy link
Contributor

@kbecciv Can you confirm this problem with new workspace?

@ishpaul777
Copy link
Contributor

ishpaul777 commented Dec 13, 2023

Proposal

Problem

Chat - Workspace avatar is greyed out in the conversation report preview

Root Cause

In src/libs/ReportUtils.ts getWorkspaceAvatar returns a empty string incase the workspace has no custom image set while it should fallback to default workspace avatar

Changes

we 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);

@NikkiWines
Copy link
Contributor

NikkiWines commented Dec 13, 2023

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 || instead of ?? here

Edit: Based on the linter failing, seems like we might not allow || instead of ??. If that's the case, then @ishpaul777's solution is good 👍

@NikkiWines
Copy link
Contributor

Yep, I'll apply your solution to my PR @ishpaul777 and you can be compensated for providing a valid solution here

@NikkiWines NikkiWines added the Bug Something is broken. Auto assigns a BugZero manager. label Dec 13, 2023
Copy link

melvin-bot bot commented Dec 13, 2023

Triggered auto assignment to @laurenreidexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels Dec 13, 2023
@Expensify Expensify deleted a comment from melvin-bot bot Dec 13, 2023
@NikkiWines
Copy link
Contributor

@laurenreidexpensify can we issue payment to @ishpaul777 for providing the solution to this deploy blocker please

@laurenreidexpensify
Copy link
Contributor

Will do, following the process where this is on prod for 7 days

@laurenreidexpensify laurenreidexpensify added Bug Something is broken. Auto assigns a BugZero manager. and removed Bug Something is broken. Auto assigns a BugZero manager. labels Dec 14, 2023
Copy link

melvin-bot bot commented Dec 14, 2023

Current assignee @laurenreidexpensify is eligible for the Bug assigner, not assigning anyone new.

Copy link

melvin-bot bot commented Dec 14, 2023

Bug0 Triage Checklist (Main S/O)

  • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
  • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
    • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
  • This bug is reproducible using the reproduction steps in the OP. S/O
    • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
    • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
  • This issue is filled out as thoroughly and clearly as possible
    • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
  • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@laurenreidexpensify laurenreidexpensify added the External Added to denote the issue can be worked on by a contributor label Dec 14, 2023
@laurenreidexpensify
Copy link
Contributor

@ishpaul777 pls apply to the job in Upwork thanks upwork.com/jobs/~014d0b71872c14469e

@mountiny
Copy link
Contributor

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

@cubuspl42
Copy link
Contributor

Reproduced on latest main. Affects iOS Native too, although I couldn't reproduce this on Android Native. Weird.

PR reviewed & approved.

@Julesssss Julesssss removed the DeployBlockerCash This issue or pull request should block deployment label Dec 14, 2023
@Julesssss
Copy link
Contributor

This is showing on the latest checklist as I didn't remove the label. This is now resolved and awaiting payment.

@mountiny mountiny removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Dec 15, 2023
@laurenreidexpensify
Copy link
Contributor

Prod for 7 days will be Dec 21st

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 labels Dec 19, 2023
@melvin-bot melvin-bot bot changed the title [$500] Web - Chat - Workspace avatar is greyed out in the conversation report preview [HOLD for payment 2023-12-26] [$500] Web - Chat - Workspace avatar is greyed out in the conversation report preview Dec 19, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Dec 19, 2023
Copy link

melvin-bot bot commented Dec 19, 2023

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Dec 19, 2023

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.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

For reference, here are some details about the assignees on this issue:

  • @ishpaul777 requires payment (Needs manual offer from BZ)

Copy link

melvin-bot bot commented Dec 19, 2023

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:

Copy link

melvin-bot bot commented Dec 26, 2023

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!

@melvin-bot melvin-bot bot removed the Overdue label Dec 26, 2023
Copy link

melvin-bot bot commented Dec 26, 2023

### Payment Summary
[Upwork Job](https://www.upwork.com/jobs/~014d0b71872c14469e)
- <Role>: @ishpaul777 paid $(<amount>) via Upwork (<Replace with offer link>)

#### BugZero Checklist (@bfitzexpensify)
- [ ] I have verified the correct assignees and roles are listed above
- [ ] I have verified that there are no duplicate or incorrect contracts on Upwork (https://www.upwork.com/ab/applicants/1735260103087415296/hired)
- [ ] I have paid out the Upwork contracts or cancelled the ones that are incorrect
- [ ] I have verified the payment summary above is correct

@bfitzexpensify
Copy link
Contributor

Offer sent @ishpaul777

@bfitzexpensify
Copy link
Contributor

Also, @ishpaul777 can you please complete the checklist in #32984 (comment)? Thanks!

@ishpaul777
Copy link
Contributor

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..

@bfitzexpensify
Copy link
Contributor

Cool, that seems fair to me. OK, let's close this one out then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor
Projects
None yet
Development

No branches or pull requests

10 participants