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
Missing To field, Send from field shows Unavailable workspace when sending invoice from chat #61637
Version Number: 9.1.42-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):shdnuihshis@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.3 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Log in with a new Gmail account.
Workspace has invoicing feature.
Go to staging.new.expensify.com
Open FAB > Send invoice.
Send invoice to any user.
Open invoice chat.
Click + > Send invoice.
Enter amount > Next.
Might need to repeat Step 5 and 6 again if the issue does not reproduce.
Expected Result:
There will be To and Send from fields.
Actual Result:
To field is missing.
Send from field shows Unavailable workspace.
👋 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:
Identify the pull request that introduced this issue and revert it.
This issue has not been updated in over 15 days. @slafortune, @mollfpr eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
@ishakakkad@mollfpr What is the status on this? Should this be closed? Did the revert correct the issue or are you still working on another fix here? Is there any money owed? For what? Thanks!
Activity
melvin-bot commentedon May 8, 2025
Triggered auto assignment to @slafortune (
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 commentedon May 8, 2025
Triggered auto assignment to @mollfpr (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 8, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 8, 2025
👋 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:
mollfpr commentedon May 8, 2025
This seems to be a regression from #60940.
cc @ishakakkad @getusha
mollfpr commentedon May 8, 2025
We will revert the PR #60940
ishakakkad commentedon May 8, 2025
@mollfpr About to create follow up PR or you want to revert it? Draft PR is ready #61690
mollfpr commentedon May 8, 2025
@ishakakkad For now, we will revert it 🙏
melvin-bot commentedon Jun 2, 2025
This issue has not been updated in over 15 days. @slafortune, @mollfpr eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
slafortune commentedon Jun 2, 2025
@ishakakkad @mollfpr What is the status on this? Should this be closed? Did the revert correct the issue or are you still working on another fix here? Is there any money owed? For what? Thanks!
mollfpr commentedon Jun 3, 2025
@slafortune We can close this since it's fixed by revert.