Report - Invisible report created if submitting track expense to WS with "Create report" rule

[jponikarchuk]

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.3.11-17
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 BrowserStack: #80915
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Account has at least one workspace.

1. Open the Expensify app.
2. Navigate to "Account" > "Expense Rules"
3. Tap on "New Rule"
4. On "If expense contains", add any merchant name.
5. On "Then apply these updates", add a category, add any name to "Add to a report named" and enable "Create report if necessary"
6. Tap on "Save Rule"
7. Create a manual expense and submit it to Self DM.
8. Tap on "Submit it to someone"
9. Select workspace chat.
10. Add the merchant name from step 4 and submit the expense.
11. Once redirected to chat, try to create a new report.
12. Note that "You already have an empty report" modal appears, despite no empty report being visible.
13. Delete the just submitted expense.
14. Try to create an empty report again.
15. Note that modal appears again.

Expected Result:

Another empty report shouldn´t be created if expense submitted to workspace, already belongs to a report with the name added as rule.

Actual Result:

An invisible empty report is created after submitting a track expense to a workspace after creating a rule with "Create report if necessary" enabled. "You already have an empty report" modal, appears when user tries to create a new report.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

@JS00001 recently merged #80915, but they are OOO right now, so I'll auto-assign someone else.

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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