-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Task - Task is not unchecked when marked as incomplete #20285
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @neil-marcellini ( |
👀 attempting to reproduce on staging and production first |
I tried reverting #19515 locally and it didn't fix it, so I don't think that PR alone caused the problem. cc @thienlnam since you're the task master. |
Will be fixed in #20014 |
Awesome thanks! |
I approved and merged the fix, and it's going to CP to staging, so I'm 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!
Issue found when executing PR #19515
Action Performed:
Precondition: User has an existing task.
Expected Result:
The task is unchecked when marked as incomplete.
Actual Result:
The task remains checked when marked as incomplete. It is only unchecked when the task is cancelled.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.24.4
Reproducible in staging?: yes
Reproducible in production?: no
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
Bug6082420_Screen_Recording_20230607_002103_New_Expensify.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: