Skip to content

[Due for payment 2025-09-26] [Due for payment 2025-09-19][$250] Reports - "Submit" button on preview, not changed to "View" when moving expense to report #63992

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.64-2
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 TestRail: #63683
Email or phone of affected tester (no customers): ibellicotest+1026@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome (mWeb - Hybrid App) / Windows 10 - Chrome
App Component: Search

Action Performed:

Prerequisite: Account has at least one workspace created and has Self DM.
Prerequisite 2: Delayed submissions and approvals enabled.

  1. Open the staging.new.expensify.com website.
  2. Open any workspace chat.
  3. Submit a manual expense to it.
  4. Navigate to Self DM.
  5. Submit a manual expense to it.
  6. Navigate to "Reports"
  7. Long tap and select the expense created in Self DM.
  8. Tap on the dropdown menu and select "Move Expense"
  9. Move the expense to the report of the expense created in workspace chat.
  10. Open the just moved expense and add a merchant and category.
  11. Return to expenses list.
  12. Note that now, both expenses on report, show "Submit" on preview insted of "View".
  13. Tap on "Submit" on any of the expenses.
  14. Note that both expenses are submitted.

Expected Result:

When moving a track expense to a report that already has an expense on a workspace, both expenses should display a "View" button on preview on "Reports" instead of the "Submit" one.

Actual Result:

When moving a track expense to a report that already has an expense on a workspace, both expenses show a "Submit" button instead of "View", on preview on "Reports" section. Also, both expenses can be submitted by tapping on "Submit" on any of the individual expenses.

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

Bug6857064_1749654379967.Both_Submit.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021933513907561041684
  • Upwork Job ID: 1933513907561041684
  • Last Price Increase: 2025-07-18
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @JmillsExpensify

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Jun 11, 2025

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (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.

  4. melvin-bot commented on Jun 11, 2025

    @melvin-bot

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

  5. github-actions commented on Jun 11, 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. nlemma commented on Jun 11, 2025

    @nlemma
    Author

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

  7. Pujan92 commented on Jun 11, 2025

    @Pujan92
    Contributor

    When moving a track expense to a report that already has an expense on a workspace, both expenses show a "Submit" button instead of "View", on preview on "Reports" section

    Isn't this correct behaviour? when the expense is moved to workspace, doesn't it need to be submitted by the requestor?

  8. arosiclair commented on Jun 11, 2025

    @arosiclair
    Contributor

    When moving a track expense to a report that already has an expense on a workspace, both expenses show a "Submit" button instead of "View", on preview on "Reports" section

    Isn't this correct behaviour? when the expense is moved to workspace, doesn't it need to be submitted by the requestor?

    Agree with this. The workspace has delayed submissions and we added expenses to an open report. The next step is to submit so that's the button that should display. Closing this out.

  9. 87 remaining items

  10. changed the title [-][Due for payment 2025-09-19][$250] Reports - "Submit" button on preview, not changed to "View" when moving expense to report[/-] [+][Due for payment 2025-09-26] [Due for payment 2025-09-19][$250] Reports - "Submit" button on preview, not changed to "View" when moving expense to report[/+] on Sep 19, 2025
  11. melvin-bot commented on Sep 19, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.15-15 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-09-26. 🎊

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

  12. melvin-bot commented on Sep 19, 2025

    @melvin-bot

    @abdulrahuman5196 @JmillsExpensify 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. melvin-bot commented on Sep 19, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@JmillsExpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1933513907561041684/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  14. melvin-bot commented on Sep 26, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@JmillsExpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1933513907561041684/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  15. JmillsExpensify commented on Sep 30, 2025

    @JmillsExpensify
    Contributor

    All confirmed and set here. Please request via New Expensify.

  16. trjExpensify commented on Oct 8, 2025

    @trjExpensify
    Contributor

    Confirming payment summary here is correct.

  17. JmillsExpensify commented on Oct 8, 2025

    @JmillsExpensify
    Contributor

    $250 approved for @Tony-MK

  18. quinthar commented on Oct 21, 2025

    @quinthar
    Contributor

    Approved $250 to @abdulrahuman5196

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