-
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
[HOLD for payment 2023-08-14] [$1000] Add Tooltip for the report actions whose actor is the workspace #21322
Comments
Triggered auto assignment to @jliexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Hey @jliexpensify, this is a follow-up issue after this PR. Don't try to reproduce this before the PR gets merged and deployed. |
If required i can work on this issue as C+ in future since the original PR and this followup issue was found during the C+ review. |
Yes, makes sense! |
Looks like the PR got deployed to Staging, so testing now. |
@cristipaval I'm confused by the instructions:
How do you do this? I found this SO but on Staging v1.3.32-5, I can only request an IOU from an individual. Is there a Beta I need to be added to?
What does "where the actor is the workspace" mean? Thanks! |
Hey @jliexpensify! The App PR which fixes this issue is already merged and deployed to staging. So you won't be able to reproduce the issue. In order to understand the testing steps, it might help you to watch the screen recordings in the PR that fixes the issue, here. |
Had some additional questions, so reached out to Cristi via DM. |
Screen.Recording.2023-06-29.at.16.23.26.movHey @jliexpensify! This is how you request money from a workspace. You can see that after requesting the money, you see in the chat the action "Workspace owes x money" In this particular case, I am requesting money from the workspace where I am an admin, that's why I can also see the button to pay the money to myself on behalf of the workspace. |
Ok, turns out this was under a beta. Got myself added and now can test: 2023-07-03_15-23-15.mp4 |
So I see the avatar and name, but this avatar is not correct right? |
@jliexpensify No that was not the issue this GH is made for. I have marked in the below image and add video. Screen.Recording.2023-07-03.at.8.05.45.PM.mov |
Ok yeah, I can also see that - it would be nice to have a tooltip as we show one for individuals: But is this also an issue? For consistency's sake, we reflect the exact same display image for other tooltips: |
Job added to Upwork: https://www.upwork.com/jobs/~012a1fc3c444f423b4 |
Current assignee @jliexpensify is eligible for the External assigner, not assigning anyone new. |
Current assignee @abdulrahuman5196 is eligible for the External assigner, not assigning anyone new. |
Current assignee @abdulrahuman5196 is eligible for the Internal assigner, not assigning anyone new. |
This proposal looks good to me as well. Assigning @Nodebrute. |
I was ooo last week and today I've been catching up for what I missed. Thanks @youssef-lr for pushing this forward. I agree with the proposal 🙇 |
@abdulrahuman5196 @cristipaval PR is ready but I am unable to login to my account due to latest changes here https://expensify.slack.com/archives/C01GTK53T8Q/p1690241973418379 |
@Nodebrute I have made a comment regarding the same here https://expensify.slack.com/archives/C01GTK53T8Q/p1690262057767139?thread_ts=1690224959.854549&cid=C01GTK53T8Q For now you can locally test by reverting the changes or making a rebase on older commit. You could also try different browsers or from different IP? |
@abdulrahuman5196 Can you please review this PR #23527? |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.50-3 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-08-14. 🎊 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:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Not overdue! |
Not a regression. Followup of this PR #20941 (comment)
YES
|
Payment Summary:
Is this correct? I don't think anyone is eligible for a bonus. |
@Nodebrute I have invited you (i think, there was only one Anusha?) but can you add your full name from upworks to your GH profile? Thanks. |
@jliexpensify correct. Accepted the offer. |
@jliexpensify I have accepted the offer. |
Everyone paid, job closed! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
You should see a tooltip with the workspace avatar and name
Actual Result:
Nothing happens
Workaround:
No workaround
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number:
Reproducible in staging?:
Reproducible in production?:
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
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: