Skip to content

[HOLD for payment 2024-12-19] [$250] Split- Deleted workspace is still shown in recents list #53392

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: 9.0.69-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
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): applausetester+232803@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

  • Account has at least two workspaces
  1. Go to staging.new.expensify.com
  2. Go to workspace chat
  3. Split an expense in the workspace chat
  4. Delete the workspace
  5. Open FAB
  6. Click Split expense under Quick action section
  7. Enter amount > Next

Expected Result:

In Step 9, the selected workspace will not display "Unavailable workspace"
In Step 11, "Hidden" will not be shown every time the selected workspace is clicked

In Step 7, the deleted workspace should not be displayed in the recents list.

Actual Result:

In Step 7, the deleted workspace is displayed in the recents list.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6682129_1733156311149.20241203_001105.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021864448103150318798
  • Upwork Job ID: 1864448103150318798
  • Last Price Increase: 2024-12-04
Issue OwnerCurrent Issue Owner: @sakluger

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 2, 2024
  2. melvin-bot commented on Dec 2, 2024

    @melvin-bot

    Triggered auto assignment to @sakluger (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. changed the title [-]Split- "Unavailable workspace" is shown for selected workspace and "Hidden" when clicked on it[/-] [+]Split- Deleted workspace is still shown in recents list[/+] on Dec 4, 2024
  4. sakluger commented on Dec 4, 2024

    @sakluger
    Contributor

    I think the actual bug here is that the deleted workspace shows up in the recents list. We shouldn't show the deleted workspace in any selectable list for choosing where to submit or who to split with.

    All the other weird behavior after selecting the deleted workspace is irrelevant because it shouldn't be there in the first place.

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Dec 4, 2024
  6. changed the title [-]Split- Deleted workspace is still shown in recents list[/-] [+][$250] Split- Deleted workspace is still shown in recents list[/+] on Dec 4, 2024
  7. melvin-bot commented on Dec 4, 2024

    @melvin-bot
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Dec 4, 2024
  9. melvin-bot commented on Dec 4, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws (External)

  10. narefyev91 commented on Dec 5, 2024

    @narefyev91
    Contributor

    Hi, I'm Nicolay from Callstack - expert contributor group - and I would like to work on this issue.

  11. 15 remaining items

  12. melvin-bot commented on Dec 12, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.74-8 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-12-19. 🎊

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

    • @Ollyws requires payment through NewDot Manual Requests
    • @narefyev91 does not require payment (Contractor)
  13. melvin-bot commented on Dec 12, 2024

    @melvin-bot

    @Ollyws @sakluger @Ollyws The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  14. sakluger commented on Dec 18, 2024

    @sakluger
    Contributor

    Hey @Ollyws, could you please complete the BZ checklist before the payment date tomorrow? Thanks!

  15. Ollyws commented on Dec 18, 2024

    @Ollyws
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on both staging and production
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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/52233/files#r1890577333

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    Test:

    1. Go to staging.new.expensify.com
    2. Go to workspace chat
    3. Split an expense in the workspace chat
    4. Delete the workspace
    5. Open FAB
    6. Click Split expense under Quick action section
    7. Enter amount > Next
    8. Select any workspace
    9. Verify that selection is working correctly
    

    Do we agree 👍 or 👎

  16. sakluger commented on Dec 18, 2024

    @sakluger
    Contributor

    Thanks for the regression test steps. I added a step to verify that the deleted workspace did not show up in the list, but otherwise, looks great. 👍

  17. melvin-bot commented on Dec 19, 2024

    @melvin-bot

    Payment Summary

    Upwork Job

    • Reviewer: @Ollyws owed $250 via NewDot
    • Contributor: @narefyev91 is from an agency-contributor and not due payment

    BugZero Checklist (@sakluger)

    • 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/1864448103150318798/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  18. Ollyws commented on Dec 19, 2024

    @Ollyws
    Contributor

    Requested in ND.

  19. garrettmknight commented on Dec 21, 2024

    @garrettmknight
    Contributor

    $250 approved for @Ollyws

  20. melvin-bot commented on Dec 24, 2024

    @melvin-bot

    @sakluger, @amyevans, @Ollyws, @narefyev91 Eep! 4 days overdue now. Issues have feelings too...

  21. sakluger commented on Dec 24, 2024

    @sakluger
    Contributor

    Thanks everyone!

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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions