Open lanitochka17 opened 2 weeks ago
Triggered auto assignment to @MitchExpensify (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.
@MitchExpensify 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
Search - RHP closes or returns to transaction thread depending on which field is edited
There is inconsistency between edit request components, some uses Navigation.dismissModal()
and some Navigation.goBack(backTo);
.
Note: There are more components that are being used for editing IOU request, we should check all components which are used in the IOU request edit flow.
We should update all components to navigate back instead of dismissing the modals. If we don't want to navigate back in all cases, we can just navigate back when editing, all components has isEditing
variable to check for that.
For MoneyRequestView
billable edit action we can use useIsReportOpenInRHP
hook and won't call Navigation.dismissModal();
in saveBillable
function.
https://github.com/Expensify/App/assets/85894871/f2df7325-80b6-422f-80a3-4ef9d36988ed
I agree this is weird; the RHP should not close after editing any field IMO. If we close the RHP we're assuming the user is finished editing that expense which may not be the case. We should drop them back in the view they were previously on which is the RHP open.
Job added to Upwork: https://www.upwork.com/jobs/~01d87627b980e14f86
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 (External
)
We can go with @Krishna2323 Proposal!
π π π C+ reviewed!
Triggered auto assignment to @NikkiWines, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
Agreed, @Krishna2323's proposal looks fine for this issue
π£ @ishpaul777 π An offer has been automatically sent to your Upwork account for the Reviewer role π Thanks for contributing to the Expensify app!
π£ @Krishna2323 π An offer has been automatically sent to your Upwork account for the Contributor role π Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review π§βπ» Keep in mind: Code of Conduct | Contributing π
Will raise PR for this tomorrow.
Update ^
@ishpaul777, PR ready for review ^
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: 1.4.85-1 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4641773 Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Expected Result:
After editing the fields, there should be consistency whether the RHP should close and return to previous page. The RHP should not close after editing any field
Actual Result:
After editing Amount, Tag and Billable field, RHP closes. While for the rest of the fields, RHP returns to transaction thread after editing the fields
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/78819774/0ef8de32-2858-4270-8aa1-5b3552a68880
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ishpaul777