You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-07-17] [$250] [Suggested Search v1] Create report appears in the Submit empty state for a user with no NewDot compatible workspaces. #64646
Version Number: Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction 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:@davidcardoza Slack conversation (hyperlinked to channel name): #Quality
Pre-requisite
The account your testing with is only a member of workspaces that aren’t NewDot compatible (don’t have the isPolicyExpenseChatEnabled: true policyNVP)
Action Performed (including steps to get an account into that state):
Create an account on expensify.com via “Sign in” button
Choose “Something else” (so a workspace isn’t created)
Go to Account > “Switch to Expensify Classic”
Create a Control workspace on OldDot (so it doesn’t have isPolicyExpenseChatEnabled: true set)
Click “Try New Expensify” to toggle back to NewDot
Click + > Create report
Observe the “coming soon” blocking modal.
Go to the Reports page
Click on Reports in the LHN
Observe the empty state doesn’t have the Create report button
Click on Submit in the LHN
Observe the empty state has the Create report button
Click on the Create report button
Observe the empty workspaces select list.
Expected Result:
Don’t show the Create report button in the Submit suggested search empty state, like we don’t the Reports empty state in this scenario whereby the user is only a member of workspaces that aren't NewDot compatible.
Actual Result:
The button shows in Submit empty state, and when clicked, navigates to an empty workspaces list.
Workaround:
None
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
@m-natarajan / @davidcardoza : I was trying to reproduce the issue. I can see that workspaces are populated in the right panel as shown in screenshot below.
was there any console error? or any network call failed?
or is it any user specific behaviour like user who is not part of any workspace?
Taking over the BZ on this one. I was investigating it in this thread (internal). It's a bug with the empty state in the new suggested search added for Submit. (CC: @JS00001@luacmartins@JmillsExpensify).
Updated the OP with how to reproduce, @kpadmanabhan.
changed the title [-][$250] [Suggested Search v1] `Create report` appears in the `Submit` empty state for a user with no NewDot compatible workspaces. [/-][+][Due for payment 2025-07-17] [$250] [Suggested Search v1] `Create report` appears in the `Submit` empty state for a user with no NewDot compatible workspaces. [/+]on Jul 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.78-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@shubham1206agra@trjExpensify 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]
[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.
[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:
The account your testing with is only a member of workspaces that aren’t NewDot compatible (don’t have the isPolicyExpenseChatEnabled: true policyNVP)
Test:
Open App
Go to the Reports page
Click on Submit in the LHN
Verify the "Create report" button is not present in the empty state UI.
Activity
melvin-bot commentedon Jun 20, 2025
Triggered auto assignment to @VictoriaExpensify (
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.MelvinBot commentedon Jun 20, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
kpadmanabhan commentedon Jun 20, 2025
@m-natarajan / @davidcardoza : I was trying to reproduce the issue. I can see that workspaces are populated in the right panel as shown in screenshot below.
trjExpensify commentedon Jun 24, 2025
Taking over the BZ on this one. I was investigating it in this thread (internal). It's a bug with the empty state in the new suggested search added for
Submit. (CC: @JS00001 @luacmartins @JmillsExpensify).Updated the OP with how to reproduce, @kpadmanabhan.
31 remaining items
[-][$250] [Suggested Search v1] `Create report` appears in the `Submit` empty state for a user with no NewDot compatible workspaces. [/-][+][Due for payment 2025-07-17] [$250] [Suggested Search v1] `Create report` appears in the `Submit` empty state for a user with no NewDot compatible workspaces. [/+]melvin-bot commentedon Jul 10, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.78-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-07-17. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jul 10, 2025
@shubham1206agra @trjExpensify 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]
trjExpensify commentedon Jul 16, 2025
This was follow-up in the suggested search project, so tests for it are being added centrally. I'm out tomorrow, so taking care of payments now.
Closing!
shubham1206agra commentedon Jul 16, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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/61170/files#r2210823802
[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.
[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:
Test:
Do we agree 👍 or 👎
garrettmknight commentedon Jul 21, 2025
$250 approved fro @shubham1206agra