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
[hold for payment 2025-12-11] [$250] Submit query lingers on other member when switching accounts via copilot #72773
Version Number: 9.2.32-1 Reproducible in staging?: Y Reproducible in production?: Y 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:@trjExpensify Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Set up accountB as a copilot
Go to Reports > Submit
Go to Settings > switch to accountB
Click the Reports page tab
Observe the from: in the query doesn’t update
Click on the Reports suggested search > then click on Submit suggested search
Observe the from: in the query updates
Expected Result:
When switching to another account via Copilot, the query filters (e.g., from:) should automatically update to reflect the newly active account immediately upon switching — without needing to reselect the search.
Actual Result:
After switching accounts, the “Submit” query lingers with the previous account’s filter until a manual interaction (reselecting the search) occurs.
Workaround:
Unknown
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:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidence2025-10-14_16-19-36.mp4Recording.1779.mp4
changed the title [-]Submit query lingers on other member when switching accounts via copilot[/-][+][$250] Submit query lingers on other member when switching accounts via copilot[/+]on Oct 16, 2025
[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: N/A
[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
Test:
Login as account A
Go to Reports
Go Account > Switch to account B
Go to Reports again
Verify that the submit query refers to the current user
Activity
melvin-bot commentedon Oct 16, 2025
Triggered auto assignment to @joekaufmanexpensify (
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.joekaufmanexpensify commentedon Oct 16, 2025
I am thinking this will be internal. Confirming in slack
joekaufmanexpensify commentedon Oct 16, 2025
It is external 👍
[-]Submit query lingers on other member when switching accounts via copilot[/-][+][$250] Submit query lingers on other member when switching accounts via copilot[/+]melvin-bot commentedon Oct 16, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021978841525789076336
melvin-bot commentedon Oct 16, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee (
External)37 remaining items
jjcoffee commentedon Dec 11, 2025
BugZero Checklist:
[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: b17531e#r172566880
[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: N/A
[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
Test:
Do we agree 👍 or 👎
jjcoffee commentedon Dec 12, 2025
@joekaufmanexpensify Just a reminder that this one's due payment 🙏
joekaufmanexpensify commentedon Dec 15, 2025
Regression issue: https://github.com/Expensify/Expensify/issues/578833
joekaufmanexpensify commentedon Dec 15, 2025
All set to pay
joekaufmanexpensify commentedon Dec 15, 2025
OG upwork job closed so I opened a new one: https://www.upwork.com/jobs/~022000612325351576682
joekaufmanexpensify commentedon Dec 15, 2025
@paulnjs offer sent in upwork!
joekaufmanexpensify commentedon Dec 15, 2025
Payment Summary
joekaufmanexpensify commentedon Dec 16, 2025
@paulnjs $250 sent and contract ended!
joekaufmanexpensify commentedon Dec 16, 2025
Upwork job closed.
joekaufmanexpensify commentedon Dec 16, 2025
@jjcoffee please request payment at your earliest convenience. Closing as this is otherwise all set 👍
trjExpensify commentedon Dec 17, 2025
approved $250 for @jjcoffee