[$250] [Awaiting Payment] Close reports for the combo of Instant Submit + No Approvals + No Payments

@garrettmknight

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: N/A
Reproducible in staging?: Y
Reproducible in production?: Y
Issue reported by: @garrettmknight
Slack conversation: https://expensify.slack.com/archives/C06ML6X0W9L/p1726136887331749?thread_ts=1725892977.799399&cid=C06ML6X0W9L

Action Performed:

Sign up with a new account
Select 'Manage my team's expenses'
Enter a first name
Enable Workflows in the workspace
Navigate to the Workflows tab
Disable Payments
Navigate to your workspace chat
Submit a manual expense

Expected Result:

Since there is no approval or payment action for anyone to take, the report should be Closed. This will result in each individual expense in this configuration creating a closed report.

Actual Result:

The expense is added to a report in the Processing state with inaccurate next steps: Waiting for [workspace admin] to pay expense(s).

Workaround:

No workaround.

Platform:

All

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021848799022838902607
Upwork Job ID: 1848799022838902607
Last Price Increase: 2024-10-22

Issue Owner

Current Issue Owner: @garrettmknight

@alexpensify

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

@srikarparsi

Because of a couple of other bugs atm we're working on elsewhere, you might want to switch to OldDot settings to get your workspace into the correct state to develop with @srikarparsi, or basically these are the three important properties on the workspace for the right condition:

scheduledSubmit=instantly
approvals = submit & close (can't remember what this one is technically, APPROVAL_MANUAL maybe 😅)
reimbursement=none

@garrettmknight

Awesome, I was able to replicate this pretty easily using @garrettmknight's steps in the issue body, didn't have to do anything in Old Dot. We just don't want the "Waiting for Srikar to pay expense(s)" because payments is not enabled right.

@garrettmknight

Awesome, I was able to replicate this pretty easily using @garrettmknight's steps in the issue body

Ah yeah, I mean it's impossible in NewDot to get the workspace into that state because of the bugs. So if you need to to test what happens to the report state when all of those three are set as such, you can get the config there via OldDot.

We just don't want the "Waiting for Srikar to pay expense(s)" because payments is not enabled right.

I think you've figured out since that the nextSteps text isn't the only scope of what's wrong with this issue. The underlying report is in the processing state instead of closed when "instant + no approvals + no payments" is configured.

@shubham1206agra

Current assignee @shubham1206agra is eligible for the External assigner, not assigning anyone new.

@shubham1206agra

@shubham1206agra offer is out to you.

https://www.upwork.com/ab/applicants/1848799022838902607/hired

Paid!

@garrettmknight

@garrettmknight @srikarparsi Be sure to fill out the Contact List!

@shubham1206agra

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[@shubham1206agra] The PR that introduced the bug has been identified. Link to the PR: N/A this has always been this way, this is more of a NewFeature than anything.
[@shubham1206agra] 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: N/A
[@shubham1206agra] A discussion in #expensify-bugs 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: N/A
[@shubham1206agra] Determine if we should create a regression test for this bug.
[@shubham1206agra] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@garrettmknight] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Took care of the checklist since it's a bit more of a New Feature issue.

@garrettmknight

@garrettmknight @srikarparsi Be sure to fill out the Contact List!

Navigation Menu

Repository navigation

[$250] [Awaiting Payment] Close reports for the combo of Instant Submit + No Approvals + No Payments #49131

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platform:

Screenshots/Videos

17 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[$250] [Awaiting Payment] Close reports for the combo of Instant Submit + No Approvals + No Payments #49131

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platform:

Screenshots/Videos

Activity

melvin-bot commented on Sep 12, 2024

trjExpensify commented on Sep 12, 2024

srikarparsi commented on Sep 13, 2024

trjExpensify commented on Sep 13, 2024

17 remaining items

melvin-bot commented on Oct 22, 2024

garrettmknight commented on Oct 22, 2024

garrettmknight commented on Oct 22, 2024

garrettmknight commented on Oct 23, 2024

melvin-bot commented on Oct 23, 2024

tgolen commented on Oct 23, 2024

garrettmknight commented on Oct 24, 2024

melvin-bot commented on Oct 24, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions