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 2024-05-09] CRITICAL [Invoice Rooms]: Update invoice rooms to use correct avatars #41261

Closed
danielrvidal opened this issue Apr 29, 2024 · 18 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 Overdue

Comments

@danielrvidal
Copy link
Contributor

danielrvidal commented Apr 29, 2024

As highlighted on this issue, we need to update the invoice rooms to use the correct Avatars.

@shawnborton highlighted the intent well in the above and I've included the direction below. But pretty much they should mirror how workspace chats work. For the large avatar, we should use the senders workspace avatar. Then, if the invoice room is shared with another workspace, we'd use that workspace avatar for the smaller avatar. If the invoice room is shared with an individual, it would show the individuals avatar. Examples below.

Workspace to Workspace:
image

Workspace to Individual:
image

cc @cristipaval can you work with the team to make sure this gets picked up?

Issue OwnerCurrent Issue Owner: @isabelastisser
@danielrvidal danielrvidal added the Daily KSv2 label Apr 29, 2024
@danielrvidal danielrvidal changed the title Update invoice rooms to use correct avatars CRITICAL [Invoice Rooms]: Update invoice rooms to use correct avatars Apr 29, 2024
@VickyStash
Copy link
Contributor

Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.
cc @cristipaval

@VickyStash
Copy link
Contributor

The PR has been opened - #41316

@VickyStash
Copy link
Contributor

NOTE: I'll be OOO 1-8th of May 🌴

@danielrvidal danielrvidal moved this to Critical in [#whatsnext] #billpay Apr 30, 2024
@cristipaval
Copy link
Contributor

PR has been merged

@danielrvidal
Copy link
Contributor Author

Yup, I tested this one and it looks good!

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels May 2, 2024
@melvin-bot melvin-bot bot changed the title CRITICAL [Invoice Rooms]: Update invoice rooms to use correct avatars [HOLD for payment 2024-05-09] CRITICAL [Invoice Rooms]: Update invoice rooms to use correct avatars May 2, 2024
Copy link

melvin-bot bot commented May 2, 2024

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

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label May 2, 2024
Copy link

melvin-bot bot commented May 2, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.69-2 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 2024-05-09. 🎊

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

@melvin-bot melvin-bot bot added Daily KSv2 and removed Weekly KSv2 labels May 8, 2024
@rushatgabhane
Copy link
Member

@cristipaval could you please attach payment summary for this issue

@cristipaval cristipaval added the Bug Something is broken. Auto assigns a BugZero manager. label May 9, 2024
Copy link

melvin-bot bot commented May 9, 2024

Triggered auto assignment to @isabelastisser (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

@cristipaval
Copy link
Contributor

cristipaval commented May 9, 2024

@isabelastisser Please help with the payment when gets due. It is due as of today

Payment summary:

@rushatgabhane for the C+ review

Note: This is not a regression. I merged the offending PR even if the design's approval was not final. We wanted to move fast and we agreed on follow-up PRs if the design requested changes

@isabelastisser
Copy link
Contributor

@rushatgabhane, can you confirm that your payment needs to be processed via NewDot?

@isabelastisser
Copy link
Contributor

Missed this:

@rushatgabhane requires payment through NewDot Manual Requests

Payment summary:

@rushatgabhane for the C+ review $500.

Copy link

melvin-bot bot commented May 9, 2024

Payment Summary

Upwork Job

BugZero Checklist (@isabelastisser)

  • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
  • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
  • I have paid out the Upwork contracts or cancelled the ones that are incorrect
  • I have verified the payment summary above is correct

@github-project-automation github-project-automation bot moved this from Critical to Done in [#whatsnext] #billpay May 9, 2024
@JmillsExpensify
Copy link

$250 approved for @rushatgabhane

@JmillsExpensify
Copy link

Ah actually, @rushatgabhane is requesting $500 and that seems correct given that this is a CRITICAL issue. @isabelastisser can you please update the payment summary with that in mind?

@isabelastisser
Copy link
Contributor

@JmillsExpensify, yes. I have already highlighted it above: #41261 (comment)

Payment summary:

Contributor: @VickyStash is from an agency-contributor and not due payment
Reviewer: @rushatgabhane owed $500 via NewDot

@melvin-bot melvin-bot bot added Overdue and removed Overdue labels May 13, 2024
@isabelastisser
Copy link
Contributor

Bump @JmillsExpensify

@JmillsExpensify
Copy link

$500 approved for @rushatgabhane

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 Overdue
Projects
Status: Done
Development

No branches or pull requests

6 participants