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
Report - After Member changed expense to non-reimbursable, the submit action has wrong owner #68555
Version Number: 9.1.94-1 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from TestRail:#63054 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: MacBook Air 15.6 Chrome, iPhone 15 Safari App Component: Money Requests
Action Performed:
Preconditions: create two gmail accounts - an Admin and a Member, Admin invited Member to the workspace
As a Member, create an expense in the workspace chat
As a Member, open expense details, switch the Reimbursable toggle off
As the Admin, navigate to the Member's workspace chat
As the Admin, click Submit, then Approve and Mark as Paid
As a Member, check the system messages in the expense details
Expected Result:
"Submitted" should be displayed under the Admin's name, since he submitted the expense
Actual Result:
"Submitted" is displayed under the Member's name after the "changed the expense to "non-reimbursable"" system message on the Member's side
Looks like we reverted the reimbursable features PR here.
@trjExpensify do you think we should leave this bug report open and hold for when the reimbursable features are live again? Or are we safe to close this one out?
changed the title [-]Report - After Member changed expense to non-reimbursable, the submit action has wrong owner[/-][+][HOLD for App PR#68581] Report - After Member changed expense to non-reimbursable, the submit action has wrong owner[/+]on Aug 15, 2025
changed the title [-][HOLD for App PR#68581] Report - After Member changed expense to non-reimbursable, the submit action has wrong owner[/-][+]Report - After Member changed expense to non-reimbursable, the submit action has wrong owner[/+]on Aug 28, 2025
@sakluger@inimaga this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Activity
melvin-bot commentedon Aug 14, 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.aadil42 commentedon Aug 14, 2025
@vincdargento, I don't have reimbursement toggle in expense.
aadil42 commentedon Aug 14, 2025
Oh. I think we need business bank account for that.
sakluger commentedon Aug 15, 2025
Looks like we reverted the reimbursable features PR here.
@trjExpensify do you think we should leave this bug report open and hold for when the reimbursable features are live again? Or are we safe to close this one out?
[-]Report - After Member changed expense to non-reimbursable, the submit action has wrong owner[/-][+][HOLD for App PR#68581] Report - After Member changed expense to non-reimbursable, the submit action has wrong owner[/+]flaviadefaria commentedon Aug 18, 2025
@daledah here's another one that might be worth checking out. Potentially for a follow-up PR.
sakluger commentedon Aug 18, 2025
Commenting for Melvin. @daledah please let me know once you've had a chance to take a closer look.
trjExpensify commentedon Aug 18, 2025
Yeah, let's retest this one.. should be testable on main in dev as the new PR was merged, but staging testing can happen after the next deploy.
16 remaining items
sakluger commentedon Aug 28, 2025
Bumped in Slack.
[-][HOLD for App PR#68581] Report - After Member changed expense to non-reimbursable, the submit action has wrong owner[/-][+]Report - After Member changed expense to non-reimbursable, the submit action has wrong owner[/+]inimaga commentedon Aug 28, 2025
Yeah, I'll be taking over this issue. @sakluger
melvin-bot commentedon Aug 28, 2025
@sakluger @inimaga this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
sakluger commentedon Sep 2, 2025
Hey @inimaga, what's the latest on this one?
inimaga commentedon Sep 2, 2025
@sakluger In progress, but not ready yet.
inimaga commentedon Sep 4, 2025
Fix got merged yesterday. Asked for a re-test of this issue here.
kavimuru commentedon Sep 4, 2025
bug is fixed
Retest.68555.mp4
sakluger commentedon Sep 5, 2025
Amazing! No contributors to pay here so we can close it out.