-
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 2024-04-15] [HOLD for payment 2024-04-09] IOU - Split btn for single contact became inactive when returned from final review #39320
Comments
Triggered auto assignment to @iwiznia ( |
👋 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:
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Split btn for single contact became inactive when returned from final review What is the root cause of that problem?When we select single participant it becomes an Lines 398 to 401 in 99cc0b6
And hence nothing changes and the tick circle does not re-render. hence we don't see the participant as selected but actually it is selected. What changes do you think we should make in order to solve the problem?When we go back from participant confirmation page we can reset the participant onyx data for type request so that when we select split on the same participant, the data is saved in onyx and hence it will re-render the list item. App/src/pages/iou/request/step/IOURequestStepConfirmation.js Lines 166 to 178 in 99cc0b6
We need to pass iouType to the participant object so that it differs between request and split iouType. We need to do change in addSingleParticipant like: {
..._.pick(option, 'accountID', 'login', 'isPolicyExpenseChat', 'reportID', 'searchText'),
selected: true,
+ iouType: iouType
}, and in addParticipantToSelection like: {
accountID: option.accountID,
login: option.login,
isPolicyExpenseChat: option.isPolicyExpenseChat,
reportID: option.reportID,
selected: true,
searchText: option.searchText,
+ iouType: iouType === CONST.IOU.TYPE.REQUEST ? CONST.IOU.TYPE.SPLIT : iouType
}, What alternative solutions did you explore? (Optional)Result033e2d49-aa23-4910-a66f-55fa648fac2b.mp4 |
Do you know what PR caused the regression @nexarvo? |
Discussing alternatives here |
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov ( |
Triggered auto assignment to @sakluger ( |
Fix was CP'd to staging 3 hours ago, lets see if we can get an applause member to help test this? 🙏 |
I cannot repro this anymore |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.58-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 2024-04-09. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 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-04-15. 🎊 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:
|
I'm a little confused and have a few questions regarding this issue:
|
Asked those questions in Slack: https://expensify.slack.com/archives/C01GTK53T8Q/p1712951143397419 |
@sakluger this issue fixed a deploy blocker and there is no regression reported for this issue. Also, creating Upwork job failed when it was made external. I think this will be a $500 as it was assigned and made external before we made standard as $250. |
This was handled without my involvement, so no payment for me |
Thank you @nexarvo! I've sent you an offer via Upwork here: https://www.upwork.com/nx/wm/offer/101873610. |
Payment Summary
BugZero Checklist (@sakluger)
|
All paid, thanks everyone! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.58-4
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause -Internal Team
Action Performed:
Precondition: user should be Signed In
Expected Result:
Selected contact should stick to the top and marked with a green checkmark when user clicked on a "Split" button for a single contact
Actual Result:
Nothing happened when user clicked on "Split" button. The split button for the single contact unresponsive on clicks
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6432434_1711785327928.Screen_Recording_2024-03-30_at_09.51.59.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: