Skip to content

[HOLD for payment 2025-02-07] [$250] Users can't submit a report that contains no reimbursable expenses  #55086

Closed

Description

@trjExpensify

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:
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @danielrvidal
Slack conversation (hyperlinked to channel name): #retain

Action Performed:

  1. Go to NewDot, create a workspace.
  2. Go to Settings > Workspaces > [Click the workspace] > Enable Workflows
  3. Go to Workflows > Enable delayed submission and set it to Manually > Enable approvals.
  4. Go to Members > invite a member to the workspace
  5. [Member] Click the green plus icon > Create expense > choose the workspace > confirm
  6. Observe the Submit button on the report preview, in the report header, and on the search page.
  7. [Member] Click Settings > Domains (to transition over to OldDot)
  8. [Member] Go to the Expenses page > click into the expense > uncheck the reimbursable checkmark
  9. [Member] open the NewDot tab > refresh
  10. Observe the Submit button is no longer visible on the report preview, report header or search page.

Expected Result:

Users should be able to see the Submit button on an expense report that contains only non-reimbursable expenses, providing they aren't all pending transactions.

Actual Result:

There's no Submit button on an expense report that contains only non-reimbursable expenses.

Note: I think this line here is culprit. Perhaps it's also in a few other places where you see the submit button.

Workaround:

They can submit via OldDot.

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

2025-01-10_18-28-51.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021877786460553153940
  • Upwork Job ID: 1877786460553153940
  • Last Price Increase: 2025-01-10
  • Automatic offers:
    • shubham1206agra | Contributor | 105671141
    • ishpaul777 | Contributor | 105671147
Issue OwnerCurrent Issue Owner: @trjExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 10, 2025
  2. self-assigned this
    on Jan 10, 2025
  3. melvin-bot commented on Jan 10, 2025

    @melvin-bot

    Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jan 10, 2025
  5. changed the title [-]Users can't submit a report that contains no reimbursable expenses [/-] [+][$250] Users can't submit a report that contains no reimbursable expenses [/+] on Jan 10, 2025
  6. melvin-bot commented on Jan 10, 2025

    @melvin-bot
  7. moved this to Product (CRITICAL) in [#whatsnext] #retainon Jan 10, 2025
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 10, 2025
  9. melvin-bot commented on Jan 10, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (External)

  10. allroundexperts commented on Jan 10, 2025

    @allroundexperts
    Contributor

    @trjExpensify Your clue is accurate.

  11. allroundexperts commented on Jan 10, 2025

    @allroundexperts
    Contributor

    We need to remove the condition here in the money report header as well. There's also a condition in the submission action that we need to remove.

  12. allgandalf commented on Jan 10, 2025

    @allgandalf
    Contributor

    @trjExpensify Your clue is accurate.

    @trjExpensify is gonna take our job away !!!!!

  13. 54 remaining items

  14. ishpaul777 commented on Feb 6, 2025

    @ishpaul777
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: https://github.com/Expensify/App/pull/51012/files#r1945412669

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: Not required

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. yes

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    N/a

    Test:

    1. Go to NewDot, create a workspace.
    2. Go to Settings > Workspaces > [Click the workspace] > Enable Workflows
    3. Go to Workflows > Enable delayed submission and set it to Manually > Enable approvals.
      4.Go to Members > invite a member to the workspace
    4. [Member] Click the green plus icon > Create expense > choose the workspace > confirm
    5. Observe the Submit button on the report preview, in the report header, and on the search page.
    6. [Member] Click Settings > Domains (to transition over to OldDot)
    7. [Member] Go to the Expenses page > click into the expense > uncheck the reimbursable checkmark
    8. [Member] open the NewDot tab > refresh
      Expected Result:
      Users should be able to see the Submit button on an expense report preview, report header or search page, providing they aren't all pending transactions.

    Do we agree 👍 or 👎

  15. trjExpensify commented on Feb 7, 2025

    @trjExpensify
    ContributorAuthor

    Regression test request created.

    Payment summary as follows:

    Confirming you're both paid via Upwork still?

  16. shubham1206agra commented on Feb 7, 2025

    @shubham1206agra
    Contributor

    @trjExpensify For this issue, yes

  17. melvin-bot commented on Feb 10, 2025

    @melvin-bot

    @trjExpensify, @lakchote, @shubham1206agra, @ishpaul777 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  18. ishpaul777 commented on Feb 10, 2025

    @ishpaul777
    Contributor

    yes still via upwork

  19. trjExpensify commented on Feb 10, 2025

    @trjExpensify
    ContributorAuthor

    Great stuff! @ishpaul777 I've paid you, @shubham1206agra you need to accept the offer.

  20. shubham1206agra commented on Feb 11, 2025

    @shubham1206agra
    Contributor

    @trjExpensify Offer accepted

  21. trjExpensify commented on Feb 11, 2025

    @trjExpensify
    ContributorAuthor

    Paid, 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.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