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
Track expense when submitted to the workspace shows "owes" in preview and "tracking" in LHN #56346
Version Number: 9.0.94-1 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 TestRail: Exp Email or phone of affected tester (no customers):applausetester+sj9032@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Mac 15.0 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to self DM.
Submit a manual expense to self DM.
Click Share it with my accountant.
Select any workspace if there are workspaces, or create a new one.
Enter merchant and submit it to the workspace chat.
Go to workspace chat.
Note that expense preview shows "spent x" and LHN shows "tracking x".
Delete the expense.
Go to self DM and submit a manual expense.
Select Submit it to someone.
Select a workspace and submit it to the workspace chat.
Go to workspace chat.
Expected Result:
If the submitted expense is supposed to be a non-track expense, the expense preview should show "owes x" and LHN should also shows "owes x".
If the submitted expense is supposed to be a track expense, the expense preview should show "spent x" and LHN should also shows "tracking x".
Actual Result:
The expense preview shows "owes x" and LHN shows "tracking x". It is giving unclear indication that the submitted expense could be 50% non-track expense and 50% track expense.
👋 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.
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!
Activity
melvin-bot commentedon Feb 4, 2025
Triggered auto assignment to @sakluger (
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 Feb 4, 2025
Triggered auto assignment to @nkuoch (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 4, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 4, 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:
Beamanator commentedon Feb 4, 2025
Helping look into this one 🤚
17 remaining items
thienlnam commentedon Feb 6, 2025
Ah given that we're overriding the reimbursable state then we should change the type based on that
sakluger commentedon Feb 7, 2025
Just checking, what's the next step here?
sakluger commentedon Feb 10, 2025
@luacmartins friendly bump, what's the next step on this GH issue?
luacmartins commentedon Feb 10, 2025
I have this PR in review https://github.com/Expensify/Auth/pull/14118 that fixes the issue
melvin-bot commentedon Mar 6, 2025
This issue has not been updated in over 15 days. @sakluger, @hungvu193, @luacmartins, @FitseTLT 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!
sakluger commentedon May 3, 2025
@luacmartins did your PR fix this issue?
FYI I'm OOO until May 19. Feel free to close if it's fixed.
luacmartins commentedon May 5, 2025
Yea, this is no longer a thing with the TradReports project. Gonna close this issue.