-
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 2024-07-10] [HOLD for payment 2024-07-02] [$250] Search - Transaction RHP dismisses when holding/unholding expense from report details page #44337
Comments
Triggered auto assignment to @neil-marcellini ( |
👋 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:
|
@neil-marcellini FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
Job added to Upwork: https://www.upwork.com/jobs/~018b190e03e676aa45 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
👀 taking a look now |
ProposalPlease re-state the problem that we are trying to solve in this issue.Search - Transaction RHP dismisses when holding/unholding expense from report details page What is the root cause of that problem?When we select hold/unhold option from report details RHP, we dismiss the modal instead of returning back. App/src/components/PromotedActionsBar.tsx Lines 68 to 71 in 3ef375f
What changes do you think we should make in order to solve the problem?
onSelected: () => {
if (!isTextHold) {
Navigation.goBack();
}
const topmostCentralPaneRoute = getTopmostCentralPaneRoute(navigationRef.getRootState() as State<RootStackParamList>);
const isReportInRHP = topmostCentralPaneRoute?.name === SCREENS.SEARCH.CENTRAL_PANE;
// dismiss the modal if isReportInRHP is false
if (!isReportInRHP && isTextHold) {
Navigation.dismissModal();
ReportUtils.changeMoneyRequestHoldStatus(reportAction);
return;
}
// Instead of dismissing the modal or calling goBack, we just provide backTo route when navigating to hold reasons page
const currentQuery = topmostCentralPaneRoute?.params as CentralPaneNavigatorParamList['Search_Central_Pane'];
ReportUtils.changeMoneyRequestHoldStatus(reportAction, ROUTES.SEARCH_REPORT.getRoute(currentQuery?.query ?? CONST.SEARCH.TAB.ALL, reportAction?.childReportID ?? ''));
}, What alternative solutions did you explore? (Optional) |
Thanks @Krishna2323! That sounds good, hired. Please get started right away. |
📣 @Krishna2323 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@Krishna2323 how's it going. When do you expect to have the PR up for review? |
@neil-marcellini, sorry for delay, the solution is much more complex than I thought, I'm about to push the changes in few minutes. |
Ah ok, thanks for the update. If you end up implementing something much different than your proposal it would be a good idea to update it. |
@neil-marcellini, I have updated my proposal to match my implementation in the PR, pls let me know if that makes sense to you, after that I will add the recordings. Resultfix_rhp_when_holding_exense.mp4 |
Yeah I think that all sounds good. I'll review the PR now. |
THe PR will be validated after being CPed |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.1-19 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-07-02. 🎊 For reference, here are some details about the assignees on this issue:
|
Issue is ready for payment but no BZ is assigned. @OfstadC you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary:Contributor: @Krishna2323 paid $250 via Upwork |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.3-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-07-10. 🎊 For reference, here are some details about the assignees on this issue:
|
$250 approved for @sobitneupane |
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: 9.0.1-10
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
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
When holding and unholding expense in Search via report details RHP, the transaction RHP will not dismiss
Actual Result:
When holding and unholding expense in Search via report details RHP, the transaction RHP dismisses
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6523376_1719260134813.20240625_041020.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @sobitneupaneThe text was updated successfully, but these errors were encountered: