[HOLD for payment 2024-03-25] [Wave Collect] [Workflows] "Delayed Submissions" toggle does not toggle off unless backed out for Collect Policy #38198
Description
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.51-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:
Action Performed:
- Access staging.new.expensify.com
- Sign into a collect policy WS Admin account
- Go to workspace setting > Workflows
- Toggle ON "Delay Submissions" then attempt to Toggle OFF
Expected Result:
User should be able to Toggle on and off with no problems
Actual Result:
The Toggle off does not work, the user must back out and return to see the toggle turn off
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence
Bug6411653_1710282341100.User_can_not_toggle_off_Delay_submissions.mp4
Issue Owner
Current Issue Owner: @trjExpensifyMetadata
Metadata
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
melvin-bot commentedon Mar 13, 2024
Triggered auto assignment to @zanyrenney (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.github-actions commentedon Mar 13, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Mar 13, 2024
Triggered auto assignment to @MonilBhavsar (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.kavimuru commentedon Mar 13, 2024
@MonilBhavsar 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.
ahmedGaber93 commentedon Mar 13, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
"Delayed Submissions" toggle does not toggle off unless backed out for Collect Policy
What is the root cause of that problem?
we always set harvesting.enable = true in
optimisticDataand after api request complete it return back with the updated value.App/src/libs/actions/Policy.ts
Lines 436 to 449 in ce3da4e
What changes do you think we should make in order to solve the problem?
we need to change harvesting.enable in
optimisticDatato be based on the toggle button new valuewe need also to reverse it in
failureData.What alternative solutions did you explore? (Optional)
MonilBhavsar commentedon Mar 13, 2024
Commented in the offending PR https://github.com/Expensify/App/pull/37441/files#r1522658153
27 remaining items
melvin-bot commentedon Mar 21, 2024
Triggered auto assignment to @trjExpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.zanyrenney commentedon Mar 21, 2024
The only thing remaining is the payout. This just a note to say that I am OOO now until April 2nd, reassigning a BZ team member to help while I am OOO.
DylanDylann commentedon Mar 25, 2024
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:
[@DylanDylann] The PR that introduced the bug has been identified. Link to the PR: #37441
[@DylanDylann] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/37441/files#r1522658153
[@DylanDylann] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: NA
[@DylanDylann] Determine if we should create a regression test for this bug. No
[@DylanDylann] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
Regression Test Proposal (If the internal engineer determines that we should create a regression test)
Do we agree 👍 or 👎
trjExpensify commentedon Mar 25, 2024
Okay, so payment summary for this PR as follows:
Offers have been sent to you both.
As for the regression test, @lakchote @mountiny do we have a more complete set to pass over to Applause as the project wraps up?
s77rt commentedon Mar 25, 2024
No payment is due for me here. I'm assigned in #37373 where payment will be handled
trjExpensify commentedon Mar 25, 2024
Cool, sounds good. Thanks for declining! @DylanDylann paid!