Skip to content

[$250] 'Recents' contacts when submitting expense does not update #48608

Description

@m-natarajan

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: n/a
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
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: @flodnv
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1724228186903849

Action Performed:

  1. Submit an expenses 3 days in a row to the same workspace
  2. Right after the 3rd time, go to submit another expense
  3. Observe that the workspace is still not in 'Recents' (although another workspace is there that I don't even use on NewDot)

Expected Result:

The workspace where I always submit to should be in 'Recents' when using it every day

Actual Result:

I don't see the workspace in 'Recents', I have to type it out every day

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021833488575321005184
  • Upwork Job ID: 1833488575321005184
  • Last Price Increase: 2024-09-17
  • Automatic offers:
    • c3024 | Contributor | 104052304
Issue OwnerCurrent Issue Owner: @Ollyws

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Fields

No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions