Skip to content

[Payment 2/21] [$500] [Wave 8] [Ideal Nav] WS - When deleting a WS offline, it is not crossed out #35702

Description

@lanitochka17

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.36-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: https://expensify.testrail.io/index.php?/tests/view/4278525&group_by=cases:section_id&group_order=asc&group_id=229065
Email or phone of affected tester (no customers): applausetester+emilio@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

  1. Access staging.new.expensify.com
  2. Sign into a valid account
  3. Tap on the Expensify logo on the top left > Expensify settings
  4. Turn off internet
  5. Tap on a 3 dot menu next to any WS and delete it while offline

Expected Result:

User expects the WS to be crossed out when deleted offline and then after returning online to disappear

Actual Result:

The WS instantly disappears

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

Bug6365190_1706899405908.WS_deleted_offline_is_not_crossed_out_.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0119aa0aa444a2b68a
  • Upwork Job ID: 1753523964291801088
  • Last Price Increase: 2024-02-02
  • Automatic offers:
    • mkhutornyi | Contributor | 28146349

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 2, 2024
  2. melvin-bot commented on Feb 2, 2024

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. github-actions commented on Feb 2, 2024

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  4. melvin-bot commented on Feb 2, 2024

    @melvin-bot

    Triggered auto assignment to @puneetlath (Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. lanitochka17 commented on Feb 2, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #wave6
    CC @greg-schroeder

  6. greg-schroeder commented on Feb 2, 2024

    @greg-schroeder
    Contributor

    Hmm. This isn't really a Wave 6 specific issue, it's kind of just general to the app

  7. greg-schroeder commented on Feb 2, 2024

    @greg-schroeder
    Contributor

    It should obviously be fixed, but I don't think it needs to be tracked on the Wave 6 board

  8. CortneyOfstad commented on Feb 2, 2024

    @CortneyOfstad
    Contributor

    @puneetlath Just let me know if there is anything you need from me as BZ! 👍

  9. 39 remaining items

  10. mananjadhav commented on Feb 21, 2024

    @mananjadhav
    Collaborator

    @CortneyOfstad This should be ready for payout. Can you help with the payout summary?

    Added a comment on the offending PR.

    @hayata-suenaga @CortneyOfstad Can one of you confirm if a test exists for the offline feedback of WS deletion already? If not, then I think it makes sense to add a regression test here.

    Copied the steps from the PR for regression test proposal.

    1. Tap on the wrench on bottom tab
    2. Turn off internet
    3. Tap on 3 dots menu next to any workspace and delete it while offline
    4. Verify that deleted workspace is crossed out
    5. Tap on 3 dots menu again
    6. Verify that 3 dots menu is disabled and not clickable
  11. CortneyOfstad commented on Feb 21, 2024

    @CortneyOfstad
    Contributor

    @mananjadhav I did not see a regression test in relation to this, so I believe that creating one should be fine. If you're confident in those steps, I'll get regression test created 👍

    Other Offline Mode tests were available in TestRail, but not removing a workspace, so would recommend adding here

    Payment summary incoming!

  12. CortneyOfstad commented on Feb 21, 2024

    @CortneyOfstad
    Contributor

    Payment Summary

    @mkhutornyi (Contributor) — paid $500 via Upwork
    @mananjadhav (C+) — to be paid $500 via NewDot

  13. mananjadhav commented on Feb 21, 2024

    @mananjadhav
    Collaborator

    Yes we used the same steps to test the PR and they worked fine.

  14. CortneyOfstad commented on Feb 21, 2024

    @CortneyOfstad
    Contributor

    Perfect! Regression test has been created here

    Also updated the title to reflect the payment date 👍

  15. changed the title [-][$500] [Wave 8] [Ideal Nav] WS - When deleting a WS offline, it is not crossed out[/-] [+][Payment 2/21] [$500] [Wave 8] [Ideal Nav] WS - When deleting a WS offline, it is not crossed out[/+] on Feb 21, 2024
  16. CortneyOfstad commented on Feb 22, 2024

    @CortneyOfstad
    Contributor

    @mananjadhav has a pay request been sent in NewDot yet?

  17. melvin-bot commented on Feb 22, 2024

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  18. hayata-suenaga commented on Feb 23, 2024

    @hayata-suenaga
    Contributor
  19. mkhutornyi commented on Feb 23, 2024

    @mkhutornyi
    Contributor

    yeah above Melvin comment is false alarm. That's because I referenced this issue here

  20. CortneyOfstad commented on Feb 23, 2024

    @CortneyOfstad
    Contributor

    This is good to close! @mananjadhav if you have any trouble getting the NewDot request through because this is closed, feel free to reopen 👍

  21. moved this from Release 1: Ideal Nav & Collect Simplfied Profile, Members, Categories, Workflows (approvals) to Done in [#whatsnext] Wave 08 - Collect Plan Adminson Feb 23, 2024
  22. JmillsExpensify commented on Feb 27, 2024

    @JmillsExpensify
    Contributor

    $500 approved for @mananjadhav based on this summary.

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions