Skip to content

Report - After Member changed expense to non-reimbursable, the submit action has wrong owner #68555

Closed

Description

@vincdargento

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

  1. As a Member, create an expense in the workspace chat
  2. As a Member, open expense details, switch the Reimbursable toggle off
  3. As the Admin, navigate to the Member's workspace chat
  4. As the Admin, click Submit, then Approve and Mark as Paid
  5. 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

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @inimaga

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 14, 2025
  2. melvin-bot commented on Aug 14, 2025

    @melvin-bot

    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.

  3. aadil42 commented on Aug 14, 2025

    @aadil42
    Contributor

    @vincdargento, I don't have reimbursement toggle in expense.

    Image
  4. aadil42 commented on Aug 14, 2025

    @aadil42
    Contributor

    Oh. I think we need business bank account for that.

  5. sakluger commented on Aug 15, 2025

    @sakluger
    Contributor

    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?

  6. 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
  7. flaviadefaria commented on Aug 18, 2025

    @flaviadefaria
    Contributor

    @daledah here's another one that might be worth checking out. Potentially for a follow-up PR.

  8. moved this to Second Cohort - CRITICAL in [#whatsnext] #migrateon Aug 18, 2025
  9. sakluger commented on Aug 18, 2025

    @sakluger
    Contributor

    Commenting for Melvin. @daledah please let me know once you've had a chance to take a closer look.

  10. trjExpensify commented on Aug 18, 2025

    @trjExpensify
    Contributor

    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.

  11. 16 remaining items

  12. sakluger commented on Aug 28, 2025

    @sakluger
    Contributor

    Bumped in Slack.

  13. 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
  14. inimaga commented on Aug 28, 2025

    @inimaga
    Contributor

    Yeah, I'll be taking over this issue. @sakluger

  15. self-assigned this
    on Aug 28, 2025
  16. melvin-bot commented on Aug 28, 2025

    @melvin-bot

    @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!

  17. sakluger commented on Sep 2, 2025

    @sakluger
    Contributor

    Hey @inimaga, what's the latest on this one?

  18. inimaga commented on Sep 2, 2025

    @inimaga
    Contributor

    @sakluger In progress, but not ready yet.

  19. inimaga commented on Sep 4, 2025

    @inimaga
    Contributor

    Fix got merged yesterday. Asked for a re-test of this issue here.

  20. kavimuru commented on Sep 4, 2025

    @kavimuru

    bug is fixed

    Retest.68555.mp4
  21. sakluger commented on Sep 5, 2025

    @sakluger
    Contributor

    Amazing! No contributors to pay here so we can close it out.

  22. moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrateon Sep 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2InternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions