Skip to content

[Due for payment 2025-06-24] [Due for payment 2025-06-23] [$250] Expense - Report field in track distance expense opens not here page #64130

Closed

Description

@mitarachim

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.1.66-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): sjdonijsdojsdod@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Account has self DM.
  1. Go to staging.new.expensify.com
  2. Create a workspace.
  3. Go to workspace chat.
  4. Click + > Create report.
  5. Go to self DM.
  6. Track a distance expense in self DM.
  7. Click on the expense preview.
  8. Click Report.

Expected Result:

Report page will open showing a list of open reports.

Actual Result:

Not here page opens.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6858668_1749782575264.20250613_104038.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021933452104789403552
  • Upwork Job ID: 1933452104789403552
  • Last Price Increase: 2025-06-13
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @CortneyOfstad

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jun 13, 2025
  2. melvin-bot commented on Jun 13, 2025

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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. github-actions commented on Jun 13, 2025

    @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 Jun 13, 2025

    @melvin-bot

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

  5. melvin-bot commented on Jun 13, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  6. 31 remaining items

  7. izarutskaya commented on Jun 13, 2025

    @izarutskaya

    Issue not reproducible on Web in 9.1.66-3

    64130.mp4
  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jun 16, 2025
  9. changed the title [-][$250] Expense - Report field in track distance expense opens not here page[/-] [+][Due for payment 2025-06-23] [$250] Expense - Report field in track distance expense opens not here page[/+] on Jun 16, 2025
  10. melvin-bot commented on Jun 16, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on Jun 16, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.66-5 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 2025-06-23. 🎊

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

    • @getusha requires payment through NewDot Manual Requests
  12. melvin-bot commented on Jun 16, 2025

    @melvin-bot

    @getusha @CortneyOfstad @getusha 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]

  13. changed the title [-][Due for payment 2025-06-23] [$250] Expense - Report field in track distance expense opens not here page[/-] [+][Due for payment 2025-06-24] [Due for payment 2025-06-23] [$250] Expense - Report field in track distance expense opens not here page[/+] on Jun 17, 2025
  14. melvin-bot commented on Jun 17, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.67-2 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 2025-06-24. 🎊

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

    • @getusha requires payment through NewDot Manual Requests
  15. melvin-bot commented on Jun 17, 2025

    @melvin-bot

    @getusha @CortneyOfstad @getusha 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]

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions