Skip to content

Members - Back button on Members opens Members page after returning from member profile #37941

Closed

Description

@kavimuru

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.49-0
Reproducible in staging?: y
Reproducible in production?: no (clicking on a member in the list is a new feature)
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

Precondition:

  • User is owner of Collect workspace.
  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Collect workspace.
  3. Go to Member.
  4. Click on any member.
  5. Click back button on the top left.
  6. Click back button on the top left again.

Expected Result:

App will return to workspace settings.

Actual Result:

App opens Members page again.

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

Bug6406304_1709857521148.Screen_Recording_20240308_082226_Chrome.mp4

View all open jobs on GitHub

Activity

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

    @melvin-bot

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

  3. github-actions commented on Mar 8, 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 Mar 8, 2024

    @melvin-bot

    Current assignee @puneetlath is eligible for the Engineering assigner, not assigning anyone new.

  5. kavimuru commented on Mar 8, 2024

    @kavimuru
    Author

    @puneetlath 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.

  6. luacmartins commented on Mar 8, 2024

    @luacmartins
    Contributor

    cc @burczu let's fix this along with #37927

  7. roryabraham commented on Mar 8, 2024

    @roryabraham
    Contributor

    Precondition: User is owner of Collect workspace [in newdot]

    AKA, NAB for now

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 8, 2024
  9. roryabraham commented on Mar 10, 2024

    @roryabraham
    Contributor

    @luacmartins @burczu can you please confirm if this issue should be on HOLD, and if so, for what? Is this the correct link? #37927

  10. luacmartins commented on Mar 11, 2024

    @luacmartins
    Contributor

    We can close this one in favor of #37927

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

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions