Skip to content

Distance - Confirm page shows Choose recipient on To field for member without address #99710

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.63-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #94316
Email or phone of affected tester (no customers): applausetester+sddd1j1d@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Log in with Expensifail accounts.
  • Add an address to workspace.
  • Enable Distance rates.
  • Select Calculate by home and office in Distance rates > Settings > Exclude commutes.
  • Invite another member without address to the workspace.
  • Create a workspace as the member and make it default workspace.
  • Perform the steps below as member.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Create a map distance expense.
  4. Click Submit to my employer.
  5. Select the invited workspace.
  6. Click outside the modal.

Expected Result:

Confirm page will show the invited workspace on To field.

Actual Result:

Confirm page shows Choose recipient on To field.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7244676_1787869554051.2.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7244676

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 27, 2026
  2. applause-bot commented on Aug 27, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/415a7a02e028e4f1a5f2ce23aaa101ef7678ac5ef1c4bb3bbf118567394f47f6

  3. melvin-bot commented on Aug 27, 2026

    @melvin-bot

    @Gonals recently merged #94316, but they are OOO right now, so I'll auto-assign someone else.

  4. github-actions commented on Aug 27, 2026

    @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.
  5. melvin-bot commented on Aug 27, 2026

    @melvin-bot

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

  6. melvin-bot commented on Aug 27, 2026

    @melvin-bot

    @robertjchen @JmillsExpensify @fedirjh you have been assigned to this deploy blocker because you reviewed the offending PR: #94316

  7. melvin-bot commented on Aug 27, 2026

    @melvin-bot

    @Gonals you have been assigned to this deploy blocker because you authored the offending PR: #94316

  8. 12 remaining items

  9. added
    ReviewingHas a PR in review
    and removed on Sep 7, 2026
  10. fedirjh commented on Sep 7, 2026

    @fedirjh
    Contributor

    PR in review

  11. melvin-bot commented on Sep 11, 2026

    @melvin-bot

    @robertjchen / @Gonals @fedirjh

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.76-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ 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]. If no checklist is needed for this issue, you can click: [no checklist button]

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.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions