-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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-22] [Pending/Scanning pattern] Update the UI for Pending and Scanning in Single Transaction ReportPreview / MoneyRequestAction #38688
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01db8df296aa6c0d99 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @thesahindia ( |
Triggered auto assignment to @shawnborton ( |
Gonna give this one to you @dannymcclain |
Updated mocks. These can all be found here in Figma. Pending TransactionReceipt Scanning"Report Status" Overview@grgia let me know if you need anything else! |
@dannymcclain are we removing the highlight row pattern? |
Yes, we decided in this thread to keep it simple to start and just go with the status pattern (no highlight). |
Rad, that makes life easy! @dannymcclain. cc @kevinksullivan shall we update the HL? I can make a few adjustments to the detailed before I pass off to SWM |
Hey, I'm an engineer from SWM, I'd like to handle this ticket |
@BrtqKr let me know if there's anything you need for this one. I updated the design doc section to reflect the final design. @dannymcclain I believe we'll need these two new icon assets for this issue: ![]() |
@dannymcclain could you also show me a mock with the report previews for this flow? By that I mean, What does it look like on the ReportPreview (parent chat) when a report has:
Are there any changes we need to make there? I believe right now it shows copy like |
Oh wow I guess you're right! Here they are:
I don't think we're changing anything there. At least I wouldn't expect us to—happy to do some mocks for those situations but I'm not 100% sure what they look like/say and I don't want to create any confusion. Is not changing anything enough for you to go on? 😅 If not I can do some investigating. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.73-7 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-22. 🎊 For reference, here are some details about the assignees on this issue:
|
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
False alert ⬆️ |
Issue is ready for payment but no BZ is assigned. @kevinksullivan you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@kevinksullivan)
|
Friendly Bump @kevinksullivan : ) |
@dannymcclain, @kevinksullivan, @grgia, @BrtqKr, @ishpaul777 Huh... This is 4 days overdue. Who can take care of this? |
@kevinksullivan I think we just need C+ payment here |
@dannymcclain, @kevinksullivan, @grgia, @BrtqKr, @ishpaul777 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
@dannymcclain, @kevinksullivan, @grgia, @BrtqKr, @ishpaul777 12 days overdue. Walking. Toward. The. Light... |
gentle bump @kevinksullivan |
handling |
job is expired so I am creating a new one. @ishpaul777 lmk when you accept |
all set |
Design Doc Section
https://docs.google.com/document/d/1hKK7emsQt4iDvP8Ohvk5aCc8gNdRelyxvbxDkXZxNRA/edit#bookmark=id.hpicdhh0ps4f
Goal
Use new UI pattern for both pending and scanning transactions.
Requirements
#38688 (comment)
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @kevinksullivanIssue Owner
Current Issue Owner: @kevinksullivanThe text was updated successfully, but these errors were encountered: