-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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-08-03] [$1000] IOS - The title field is cleared when the Confirm task button is pressed #22078
Comments
Triggered auto assignment to @laurenreidexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.The title field is cleared when the Confirm task button is pressed What is the root cause of that problem?The root cause of the problem is the usage of What changes do you think we should make in order to solve the problem?We can just remove this line of code which will fix the issue. |
Job added to Upwork: https://www.upwork.com/jobs/~01f1a312f3e2545b22 |
Current assignee @laurenreidexpensify is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @0xmiroslav ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.IOS - The title field is cleared when the Confirm task button is pressed What is the root cause of that problem?Before dismissing modal What changes do you think we should make in order to solve the problem?We can call App/src/pages/tasks/NewTaskPage.js Line 69 in 754723d
Like this useEffect(() => clearOutTaskInfo, []); What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.The title field is cleared What is the root cause of that problem?We're clearing the task info here after confirming. The screen transition takes some time so we can see the values are cleared. What changes do you think we should make in order to solve the problem?We should run the What alternative solutions did you explore? (Optional)Both Title and Description will be benefit from the same fix as well. Another approach is to:
If we don't use the ref, the task values will be cleared also when going back to previous page, which is not desirable. |
@0xmiroslav what do you think about these two proposals ^^ |
@0xmiroslav bump on proposal review, thanks |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Messaged @0xmiroslav in Slack :) |
@dukenv0307's alternative solution looks good to me. |
Triggered auto assignment to @robertjchen, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@robertjchen @laurenreidexpensify @0xmiroslav this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Awaiting updated proposal w/ all occurrences where the similar issue happens per: #22078 (comment) |
@laurenreidexpensify I think the original reporter should have been paid here as I reported the issue earlier. |
Thanks for organizing all the details, we'll review this! 👀 |
Still getting around to evaluating this, thanks for everyone's patience! 🙏 |
@robertjchen Bump |
@robertjchen have you had a chance to review this? thanks |
@robertjchen Any update here? |
Appreciate your patience, circling back to this and will respond before end of day. |
Okay, my analysis on the situation is:
cc: @laurenreidexpensify for final confirmation and next steps! 👍 |
@robertjchen what about me for reviewing 2nd PR? I took over based on #22078 (comment) |
@situchan Updated my comment! 👍 |
@laurenreidexpensify let me know if you have any questions! |
Payment Summary:
@0xmiroslav can you confirm the regression checklist steps? |
No PR caused regression. Original issue was minor UI bug, though root cause was a bit critical. Regression Test Proposal
|
@0xmiroslav offer sent 👍 |
Payments have all been issued, closing. |
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:
The title field should not be cleared
Actual Result:
The title field is cleared
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.34-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:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
title-cleared.1.MP4
ios.ass.task.0107.mp4
Expensify/Expensify Issue URL:
Issue reported by: @aman-atg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688216349574539
[View all open jobs on GitHub](https://github.com/Expensify/App/issues?q=is%3Aopen+is% 3Aissue+label%3A%22Help+Wanted%22)
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: