Skip to content

[Due for payment 2025-04-17] IOU - After moving IOU the status in expense details is inconsistent on the Admin side #59210

Closed

Description

@izarutskaya

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: v9.1.19-5
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: #58078
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Pixel 7 Pro /Android 15
App Component: Money Requests

Action Performed:

Pre-requisite: A workspace with an admin and an employee
The workflow setting: enables Approvals, Delay Submissions is set to Manual, and enables Payment.

  1. [Employee] Request money (IOU) from admin - DM
  2. [Employee] Open the IOU report, copy the URL, add /change-workspace to the end of it, and send it as a message to the report
  3. [Employee] Click the URL to open the Change Workspace RHP
  4. Move the IOU report to the workspace the employee is a member of

Expected Result:

Verify that the IOU report was converted to an Expense report
Verify that the report preview was removed from the DM and added to the user's workspace chat

Actual Result:

The expense detail on the employee status: "waiting for Admin approve expense", but in the Admin shows the "Pay with expensify" button, and below still has "waiting for You approve expense"

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6783919_1743070001902.PR58078.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @adelekennedy

Activity

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

    @melvin-bot

    Triggered auto assignment to @adelekennedy (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 Mar 27, 2025

    @melvin-bot

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

  4. melvin-bot commented on Mar 27, 2025

    @melvin-bot

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

  5. github-actions commented on Mar 27, 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. izarutskaya commented on Mar 27, 2025

    @izarutskaya
    Author

    Production

    bandicam.2025-03-27.12-47-42-012.mp4
  7. removed
    DeployBlockerIndicates it should block deploying the API
    on Mar 27, 2025
  8. 39 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Apr 10, 2025
  10. changed the title [-]IOU - After moving IOU the status in expense details is inconsistent on the Admin side[/-] [+][Due for payment 2025-04-17] IOU - After moving IOU the status in expense details is inconsistent on the Admin side[/+] on Apr 10, 2025
  11. melvin-bot commented on Apr 10, 2025

    @melvin-bot

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

  12. melvin-bot commented on Apr 10, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.25-4 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-04-17. 🎊

  13. melvin-bot commented on Apr 10, 2025

    @melvin-bot

    @luacmartins @adelekennedy @luacmartins 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]

  14. melvin-bot commented on Apr 17, 2025

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  15. luacmartins commented on Apr 18, 2025

    @luacmartins
    Contributor

    no payments needed for this one. closing.

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions