Skip to content

[HOLD for payment 2024-07-22] [$250] Search - "Scanning" appears in Description field when expense is scanning #44596

Closed

Description

@izarutskaya

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.0.3-1
Reproducible in staging?: Y
Reproducible in production?: N
Found when executing PR : #44190
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Precondition:

  • Account has no expenses (or has expenses with no merchant).
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit a scan expense.
  4. While the expense is scanning, go to Search.

Expected Result:

"Scanning" will not appear in Description field because "Scanning" is not in Description field in transaction thread.

Actual Result:

"Scanning" appears in Description field when "Scanning" is not in Description field in transaction thread.

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

Bug6526894_1719536704148.bandicam_2024-06-28_09-01-21-976.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01ed996315e0843cef
  • Upwork Job ID: 1815474885633659701
  • Last Price Increase: 2024-07-22
Issue OwnerCurrent Issue Owner: @

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jun 28, 2024
  2. melvin-bot commented on Jun 28, 2024

    @melvin-bot

    Triggered auto assignment to @cristipaval (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on Jun 28, 2024

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

  4. github-actions commented on Jun 28, 2024

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. izarutskaya commented on Jun 28, 2024

    @izarutskaya
    Author

    @sakluger I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  6. izarutskaya commented on Jun 28, 2024

    @izarutskaya
    Author

    We think this issue might be related to the #collect project.

  7. izarutskaya commented on Jun 28, 2024

    @izarutskaya
    Author

    Production
    image

  8. 23 remaining items

  9. changed the title [-]Search - "Scanning" appears in Description field when expense is scanning[/-] [+][HOLD for payment 2024-07-22] [$250] Search - "Scanning" appears in Description field when expense is scanning[/+] on Jul 22, 2024
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 22, 2024
  11. melvin-bot commented on Jul 22, 2024

    @melvin-bot

    ⚠️ This issue has had its price increased by 4x or more. Please review the issue and ensure the price is correct.

  12. melvin-bot commented on Jul 22, 2024

    @melvin-bot

    Current assignee @mollfpr is eligible for the External assigner, not assigning anyone new.

  13. melvin-bot commented on Jul 22, 2024

    @melvin-bot

    Upwork job price has been updated to $250

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed
    ReviewingHas a PR in review
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jul 22, 2024
  15. etCoderDysto commented on Jul 22, 2024

    @etCoderDysto
    Contributor

    Oh I think automation failed here and we still need to process the payment. Updating the issue

    I don't think there are any payments to be made here. This issue was a regression from my PR. And I and C+ fixed the issue.

  16. luacmartins commented on Jul 22, 2024

    @luacmartins
    Contributor

    Ah I see, then yes we're good to close since that'll be handled in the original issue. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringExternalAdded to denote the issue can be worked on by a contributorMonthlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions