Skip to content

[$250] Don't allow the Approver on a policy to leave a workspace chat #43852

Closed

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.84-2
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
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

  • User is invited to a workspace
  1. Go to staging.new.expensify.com
  2. Go to workspace chat as workspace member
  3. Go offline
  4. Go to + > Submit expense > Manual
  5. Proceed to confirmation page
  6. Click on the workspace chat
  7. Click Leave

Expected Result:

The option to leave should not show up for a workspace chat unless you were invited into the room by a mention and not part of the approval workflow

Actual Result:

You see the option to leave the room

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

20240618_000151.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0194a281c56dd7cd3e
  • Upwork Job ID: 1802768531325940224
  • Last Price Increase: 2024-07-08
Issue OwnerCurrent Issue Owner: @sobitneupane

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Jun 17, 2024
  2. melvin-bot commented on Jun 17, 2024

    @melvin-bot

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

  3. github-actions commented on Jun 17, 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. lanitochka17 commented on Jun 17, 2024

    @lanitochka17
    Author

    @thienlnam 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

  5. lanitochka17 commented on Jun 17, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #wave-collect - Release 1

  6. thienlnam commented on Jun 17, 2024

    @thienlnam
    Contributor

    This seemed like it would have been from a BE PR, but I haven't seen anything that would change how this works. Going to open up externally for some more eyes on the App checklist

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jun 17, 2024
  8. melvin-bot commented on Jun 17, 2024

    @melvin-bot
  9. changed the title [-]Expense - Expense can still be submitted after leaving workspace chat[/-] [+][$250] Expense - Expense can still be submitted after leaving workspace chat[/+] on Jun 17, 2024
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 17, 2024
  11. 44 remaining items

  12. melvin-bot commented on Jul 4, 2024

    @melvin-bot

    @sobitneupane, @thienlnam, @isabelastisser Whoops! This issue is 2 days overdue. Let's get this updated quick!

  13. isabelastisser commented on Jul 8, 2024

    @isabelastisser
    Contributor

    Bump @mvtglobally, can you please retest? Thanks!

  14. melvin-bot commented on Jul 8, 2024

    @melvin-bot

    📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

  15. melvin-bot commented on Jul 8, 2024

    @melvin-bot

    @sobitneupane, @thienlnam, @isabelastisser 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  16. sobitneupane commented on Jul 9, 2024

    @sobitneupane
    Contributor
  17. isabelastisser commented on Jul 10, 2024

    @isabelastisser
    Contributor

    Bump @mvtglobally. can you please retest? thanks!

  18. moved this to Release 1: Spring 2024 (May) in [#whatsnext] #wave-collecton Jul 10, 2024
  19. mvtglobally commented on Jul 11, 2024

    @mvtglobally

    Issue not reproducible during KI retests. (Second week)

  20. kbecciv commented on Jul 11, 2024

    @kbecciv

    Here is a video, issue no longer reproducible

    Screen.Recording.2024-07-10.at.9.39.38.PM.mp4
  21. moved this from Release 1: Spring 2024 (May) to Done in [#whatsnext] #wave-collecton Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions