-
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-07-28] [HOLD for payment 2023-07-26] Clicking on 'From' link navigates to main chat rather than navigating to the previous IOU thread report #23102
Comments
Triggered auto assignment to @flaviadefaria ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @neil-marcellini ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Clicking on 'From' link navigates to main chat rather than navigating to the previous IOU thread report What is the root cause of that problem?In App/src/components/HeaderWithBackButton/index.js Lines 83 to 87 in f74512d
In this case if What changes do you think we should make in order to solve the problem?We shall change it to -
In this case, if report is null, parentReport will be used. But for our case(in this bug) we want to be redirected to ResultCorrect.redirect.mp4What alternative solutions did you explore? (Optional) |
Huh why did this get changed to daily? |
This happens when someone not assigned submits proposal |
👀 I'm looking into this now. |
@BhuvaneshPatil thanks for your proposal, I think you're on the right track, but I think reversing the OR statement would cause a problem. We need to understand why we pass the parentReport sometimes. I see it was added in this commit. The reasoning in the proposal is the following.
That's no longer, true, now we simply pass the report. I'm going to remove the |
@neil-marcellini I was also analysing the root cause of this issue and I came to the same conclusion. This doesn't exist on prod because it was removed in this PR but now in this PR it was added back. I will be happy to open a PR for this right now if you want me to. |
Nice thanks for finding the PR that added it back. That's the source of the regression. I have a PR in the works now. |
Thanks for informing @neil-marcellini . |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.43-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 2023-07-28. 🎊 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.
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
@allroundexperts would you please help me out by taking care of the checklist above? Usually C+ does this. |
Sure thing. Will do this today! |
@allroundexperts @neil-marcellini is the below correct? @Natnael-Guchima = $250 (reporting bonus - UW) Also @allroundexperts can you please fill out the checklist above? Thanks! |
Bump on the above @allroundexperts. |
@flaviadefaria Is the checklist needed here? I just did a PR review of an internal employee here. |
@neil-marcellini should you be filling it out then? You are the one tagged so maybe that's how it works for internal issues? |
IMO C+ should always fill out the checklist. Seems like a reasonable ask for $1,000. I will do it this time to keep things moving. |
I think we should add a regression test because it's very easy to test and it's a core feature of our chat app now; people will be going into threads and going back to the parent often. |
Regression Test Proposal
Do we agree 👍 or 👎 |
Are these payment amounts correct? Since there's no contributor assigned I'm assuming we're only paying the bug reporter and the C+ for reviewing the PR? |
Hi @neil-marcellini! |
Reviewed details for @allroundexperts. These details are accurate based on summary from Business Reviewer and are now approved for payment in NewDot. |
Offer sent to @Natnael-Guchima! |
Accepted the offer. Thanks @flaviadefaria |
Paid so closing this! |
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:
User should be navigated to to the IOU thread report where user was navigated on step 5
Actual Result:
User is navigated to main chat
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.42-5
Reproducible in staging?: y
Reproducible in production?: n
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
Screencast.from.2023-07-18.17-29-49.webm
Recording.1283.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689691734672829
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: