Skip to content

[Due for payment 2025-06-02] [Due for payment 2025-05-30] [Report Creation UI] [$250] Expense - Not here page opens when admin clicks Move expense in member's report #62575

Closed

Description

@nlemma

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.49-5
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): sjdnionsdojds@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.4 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Admin invites member to the workspace.
  • Admin account does not have any workspace expense report in any status (open, closed, processing etc).
  1. Go to staging.new.expensify.com
  2. [Member] Go to workspace chat.
  3. [Member} Create an expense in the workspace chat.
  4. [Admin] Go to workspace chat with member.
  5. [Admin] Click on the expense preview.
  6. [Admin] Click More > Move expense.

Expected Result:

Report list will open with the current report selected.

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

Bug6839124_1747913566720.20250522_192759.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021925612414512804213
  • Upwork Job ID: 1925612414512804213
  • Last Price Increase: 2025-05-22
  • Automatic offers:
    • twilight2294 | Contributor | 107414077
Issue OwnerCurrent Issue Owner: @slafortune

Activity

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

    @melvin-bot

    Triggered auto assignment to @slafortune (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. melvin-bot commented on May 22, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 22, 2025

    @melvin-bot

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

  5. github-actions commented on May 22, 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.
  6. grgia commented on May 22, 2025

    @grgia
    Contributor

    Likely #62270

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on May 22, 2025
  8. 54 remaining items

  9. changed the title [-][Due for payment 2025-05-30] [Report Creation UI] [$250] Expense - Not here page opens when admin clicks Move expense in member's report[/-] [+][Due for payment 2025-06-02] [Due for payment 2025-05-30] [Report Creation UI] [$250] Expense - Not here page opens when admin clicks Move expense in member's report[/+] on May 26, 2025
  10. melvin-bot commented on May 26, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 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-02. 🎊

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

  11. melvin-bot commented on May 26, 2025

    @melvin-bot

    @grgia @slafortune @jnowakow / @twilight2294 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]

  12. twilight2294 commented on May 29, 2025

    @twilight2294
    Contributor

    Payment on 05/30, there was some problem with automation i think

  13. melvin-bot commented on Jun 2, 2025

    @melvin-bot

    @slafortune Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  14. slafortune commented on Jun 2, 2025

    @slafortune
    Contributor

    @twilight2294 can you please complete the checklist so this can be paid?

  15. twilight2294 commented on Jun 2, 2025

    @twilight2294
    Contributor

    @slafortune can you pay me please, I am not a C+, do you still want me to fill the checklist ?

  16. slafortune commented on Jun 3, 2025

    @slafortune
    Contributor

    @jnowakow does not require payment, Expert Contributor
    @twilight2294 Paid $250 via Upworks ✅

  17. moved this from Second Cohort - HIGH to Done in [#whatsnext] #migrateon Jun 3, 2025
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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions