-
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-10-16] [HOLD for payment 2023-10-13] [$500] LOW: Web - Clicking on "Replace" for a paid scan request results in the scan modal opening and then closing automatically #27965
Comments
Job added to Upwork: https://www.upwork.com/jobs/~0106bd3efbb87edef7 |
Triggered auto assignment to @puneetlath ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @NicMendonca ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @burczu ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Clicking on "Replace" for a paid scan request results in the scan modal opening and then closing automatically What is the root cause of that problem?This happens because in AttachmentModal.js we allow the user to navigate to the edit request route without checks. The menuItem does not have any checks: App/src/components/AttachmentModal.js Lines 361 to 369 in 65fd435
This results in navigating to EditRequestPage.js here if App/src/pages/EditRequestPage.js Lines 96 to 103 in e24e431
This causes the flash. What changes do you think we should make in order to solve the problem?
Screencast.from.22-09-23.07.38.47.AM.IST.webm
Screencast.from.22-09-23.07.50.41.AM.IST.webmThis would also be better UX as when accessed from other paths, instead of just dismissing a clear message is shown.
What alternative solutions did you explore? (Optional)xx |
ProposalPlease re-state the problem that we are trying to solve in this issue.When clicking on "Replace" for a paid request, the modal should not show the "Replace" option. What is the root cause of that problem?The settled report cannot be edited. It's checked here: App/src/pages/EditRequestPage.js Lines 96 to 103 in e24e431
Now in What changes do you think we should make in order to solve the problem?We should check if the request was settled and shouldn't show the "Replace" menu item if it's settled. In
and then check |
📣 @huzaima! 📣
|
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
ProposalPlease re-state the problem that we are trying to solve in this issue.replace image option appears even after paid What is the root cause of that problem?We always set App/src/components/AttachmentModal.js Lines 361 to 370 in 47d10e6
What changes do you think we should make in order to solve the problem?We should check if the request cannot edit, we will remove
App/src/components/AttachmentModal.js Line 361 in 47d10e6
What alternative solutions did you explore? (Optional)NA ResultScreencast.from.21-09-2023.16.34.49.webm |
This comment was marked as off-topic.
This comment was marked as off-topic.
✅ Contributor details stored successfully. Thank you for contributing to Expensify! |
taking over for Puneet as it's part of wave4! |
@burczu lets get these proposals reviewed soon! 🙏 |
@burczu let's get this done today! |
@dylanexpensify yes, I'm on it right now actually |
I've just reviewed all the proposals and I believe that all of them recognized the root case correctly. In my opinion removing the The proposal from @dukenv0307 presents the solution in the most comprehensive way - I like it the most and would recommend proceeding with it. However the proposall from @neonbhai (Solution 2) is very similar (but not described that well) and it's hard to tell who was first here - I've checked the editing history and it seems the detailed explanation was added after @dukenv0307. So, whoever will review these proposals after me, please take it into consideration when making the final decision. 🎀 👀 🎀 C+ reviewed |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.78-4 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-10-13. 🎊 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.
For reference, here are some details about the assignees on this issue:
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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.79-5 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-10-16. 🎊 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.
For reference, here are some details about the assignees on this issue:
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:
|
Payment summary:
|
reviewing today! |
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:
|
payment upcoming! |
@burczu, @Li357, @dylanexpensify, @dukenv0307 Huh... This is 4 days overdue. Who can take care of this? |
@burczu, @Li357, @dylanexpensify, @dukenv0307 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@burczu, @Li357, @dylanexpensify, @dukenv0307 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
@ayazhussain79 please apply to job for reporter payment! |
@dylanexpensify applied on upwork, Thank you |
offer sent @ayazhussain79! |
done! |
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:
When clicking on "Replace" for a paid scan request, the scan modal should either remain open or not open at all, depending on the intended functionality
Actual Result:
Clicking on "Replace" for a paid scan request causes the scan modal to open briefly and then close automatically
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.72.8
Reproducible in staging?: y
Reproducible in production?: y
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
screen-recording-2023-09-20-at-22122-pm_sWMvL9a8.mp4
Recording.4676.mp4
Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695202167946769
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: