Skip to content

[HOLD for payment 2024-06-28] Disabling Delayed Submission in NewDot turns off Scheduled Submit instead of setting Instant Submit #42685

Description

@garrettmknight

Action Performed:

  1. Create new workspace in NewDot
  2. Disable Delayed Submission

Expected Result:

Workspace has Scheduled Submit enabled and 'Instantly' selected.

Actual Result:

Workspace has Scheduled Submit disabled.

Workaround:

Set 'Instantly' in OldDot, no workaround in NewDot.

Platform:

All

  • Version Number: v1.4.76-3
  • Logs: See how to search logs here
  • Notes/Photos/Videos: Any additional supporting documentation
  • Is this issue reproducible in staging, production or both? both

cc @lakchote @Beamanator

Issue OwnerCurrent Issue Owner: @adelekennedy

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 28, 2024
  2. melvin-bot commented on May 28, 2024

    @melvin-bot

    Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. self-assigned this
    on May 29, 2024
  4. trjExpensify commented on Jun 4, 2024

    @trjExpensify
    Contributor

    Can the App PR come off hold here?

  5. moved this from HOT PICKS to Release 2: Summer 2024 (Aug) in [#whatsnext] #wave-collecton Jun 4, 2024
  6. parasharrajat commented on Jun 20, 2024

    @parasharrajat
    Member

    I was C+ on the PR. Please assign me.

  7. 5 remaining items

  8. melvin-bot commented on Jun 21, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.85-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 2024-06-28. 🎊

    For reference, here are some details about the assignees on this issue:

  9. melvin-bot commented on Jun 21, 2024

    @melvin-bot

    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:

    • [@parasharrajat] The PR that introduced the bug has been identified. Link to the PR:
    • [@parasharrajat] 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:
    • [@parasharrajat] 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:
    • [@parasharrajat] Determine if we should create a regression test for this bug.
    • [@parasharrajat] 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.
    • [@adelekennedy] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  10. parasharrajat commented on Jun 22, 2024

    @parasharrajat
    Member

    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:

    • [@parasharrajat] The PR that introduced the bug has been identified. Link to the PR: It is refactor.
    • [@parasharrajat] 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: NA
    • [@parasharrajat] 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
    • [@parasharrajat] Determine if we should create a regression test for this bug. YES
    • [@parasharrajat] 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 Steps

    1. Create new workspace in NewDot
    2. Disable Delayed Submission
    3. Workspace has Scheduled Submit enabled and 'Instantly' selected, on OldDot.

    Do you agree 👍 or 👎 ?

  11. melvin-bot commented on Jun 28, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@adelekennedy)

    • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  12. adelekennedy commented on Jul 1, 2024

    @adelekennedy
    Contributor

    payment summary is correct, payments due:

    $250 @parasharrajat (NewDot)

  13. parasharrajat commented on Jul 1, 2024

    @parasharrajat
    Member

    Payment requested as per #42685 (comment)

  14. adelekennedy commented on Jul 1, 2024

    @adelekennedy
    Contributor
  15. moved this from Release 2: Summer 2024 (Aug) to Done in [#whatsnext] #wave-collecton Jul 1, 2024
  16. JmillsExpensify commented on Jul 2, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @parasharrajat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2InternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions