Skip to content

[SMARTSCAN] MEDIUM: Receipt Scan Failures Polish #26832

Closed

Description

@trjExpensify

👋 @Gonals there's a bit of a diff from the design doc on this one. Can you help clean this up post-SaaStr? Thanks!

image
  • 1. The error messages should be in-line beneath the field in error

  • 2. The title of the failed request should update from Receipt scan in progress... to Receipt missing details

  • 3. A system message from Expensify should be added to the transaction thread when the receipt scan fails to notify the member

  • 4. The RBR red dot should be on the request row for member only (not the expense report row or for the admin as well)

image image

CC: @JmillsExpensify @shawnborton

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~017bd7a39e34a6a3cb
  • Upwork Job ID: 1699189929552527360
  • Last Price Increase: 2023-09-05

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 5, 2023
  2. melvin-bot commented on Sep 5, 2023

    @melvin-bot

    Current assignee @Gonals is eligible for the Engineering assigner, not assigning anyone new.

  3. melvin-bot commented on Sep 5, 2023

    @melvin-bot

    Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

  4. melvin-bot commented on Sep 5, 2023

    @melvin-bot
  5. melvin-bot commented on Sep 5, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  6. melvin-bot commented on Sep 5, 2023

    @melvin-bot

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @sobitneupane (Internal)

  7. shawnborton commented on Sep 5, 2023

    @shawnborton
    Contributor

    Another quick one - if there is no Amount, we should make the Amount label use our standard font size (15px) and float to the vertical center of the push row. This really should be a global component we share everywhere, I feel like we keep having inconsistencies here.

  8. 36 remaining items

  9. Gonals commented on Oct 30, 2023

    @Gonals
    Contributor

    There's actually a problem with that one. It looks posted by _FAKE_ instead of notifications@expensify.com. I believe it is caused by how notifications@expensify.com was created (closed from the get-go) and have a PR in review to (hopefully) fix it.

  10. dylanexpensify commented on Oct 30, 2023

    @dylanexpensify
    Contributor

    Ahhh useful to know, thanks @Gonals! Mind linking PR here for good measure? 🙇‍♂️

  11. Gonals commented on Oct 30, 2023

    @Gonals
    Contributor
  12. changed the title [-][Scan Receipt] [MEDIUM] Receipt Scan Failures Polish[/-] [+][SMARTSCAN] MEDIUM: Receipt Scan Failures Polish[/+] on Nov 7, 2023
  13. dylanexpensify commented on Nov 7, 2023

    @dylanexpensify
    Contributor

    Checking in, did that Auth PR linked above fix the issue @Gonals?

  14. melvin-bot commented on Nov 23, 2023

    @melvin-bot

    This issue has not been updated in over 15 days. @trjExpensify, @Gonals, @sobitneupane eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  15. trjExpensify commented on Nov 23, 2023

    @trjExpensify
    ContributorAuthor

    Yes, that's fixed. There's a separate issue to add the Expensify logo and give it a name. Closing.

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.EngineeringInternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in reviewSmartScanWave5-free-submittersWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions