Skip to content

WS Members - 'Back' leads to invite members page instead of Settings after delete added user #35776

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
4 of 6 tasks
lanitochka17 opened this issue Feb 4, 2024 · 7 comments
Closed
4 of 6 tasks
Assignees

Comments

@lanitochka17
Copy link

lanitochka17 commented Feb 4, 2024

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] 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:
Email or phone of affected tester (no customers): [email protected]
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:

Action Performed:

  1. Open iOS/Android App or go to staging.new.expensify.com on mobile Chrome / Safari
  2. Login with any account
  3. Create existing workspace or go to existing one
  4. Got to WS > Members > Invite new member
  5. Select and invite any members
  6. Remove added members
  7. Tap 'Back' button on top left corner

Expected Result:

User goes to the WS Settings page

Actual Result:

User goes to the 'Invite new members' page

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

Bug6366472_1707014385055.iOS-Back-after-delete-new-ws-members.mp4

View all open jobs on GitHub

@lanitochka17 lanitochka17 added the DeployBlockerCash This issue or pull request should block deployment label Feb 4, 2024
Copy link
Contributor

github-actions bot commented Feb 4, 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:

  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.

Copy link

melvin-bot bot commented Feb 4, 2024

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

@lanitochka17
Copy link
Author

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

@mountiny mountiny moved this to Release 1: Ideal Nav & Collect Simplfied Profile, Members, Categories, Workflows (approvals) in [#whatsnext] Wave 08 - Collect Plan Admins Feb 5, 2024
@mountiny mountiny added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Feb 5, 2024
@mountiny mountiny assigned mountiny and unassigned pecanoro Feb 5, 2024
@mountiny
Copy link
Contributor

mountiny commented Feb 5, 2024

I think this is same generic issue with the goBack we are aware of @adamgrzybowski is working on a fix

@melvin-bot melvin-bot bot added the Overdue label Feb 7, 2024
@mountiny mountiny added Weekly KSv2 and removed Daily KSv2 labels Feb 7, 2024
@mountiny
Copy link
Contributor

mountiny commented Feb 7, 2024

@adamgrzybowski is working on the back issues, can you please comment here?

@melvin-bot melvin-bot bot removed the Overdue label Feb 7, 2024
@melvin-bot melvin-bot bot removed the Weekly KSv2 label Mar 4, 2024
Copy link

melvin-bot bot commented Mar 4, 2024

This issue has not been updated in over 15 days. @mountiny eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

@mountiny
Copy link
Contributor

This is not repro anymore after the ideal nav v2 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Archived in project
Status: Release 1: Ideal Nav & Collect Simplfied Profile, Members, Categories, Workflows (approvals)
Development

No branches or pull requests

3 participants