Skip to content

[HOLD for payment 2024-05-08] CRITICAL: [Track expense] [$250] Make SmartScanning expense-level thread less confusing #40366

Closed

Description

@quinthar

Problem:

When you scan a receipt, it shows this in the selfDM:

image

When you click into it (sorry, different receipt) it looks like:

image

This is pretty confusing as:

  • The title is Tracking $0.00
  • It shows Amount * Cash and Merchant fields, even though they are blank

Solution:

Please:

  1. Make the header show Scan in progress... as the title while scanning, to match the scan preview in the parent chat
  2. Show Scanning... inside Amount * Cash and Merchant fields while scanning
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0145ed848b68697b8d
  • Upwork Job ID: 1782614171256602624
  • Last Price Increase: 2024-04-23
  • Automatic offers:
    • fedirjh | Reviewer | 0
    • Nodebrute | Contributor | 0

Activity

  1. converted this from a draft issue on Apr 17, 2024
  2. changed the title [-]CRITICAL: [Track expense] Make SmartScanning expense-level thread less confusing[/-] [+]WIP: CRITICAL: [Track expense] Make SmartScanning expense-level thread less confusing[/+] on Apr 17, 2024
  3. changed the title [-]WIP: CRITICAL: [Track expense] Make SmartScanning expense-level thread less confusing[/-] [+]CRITICAL: [Track expense] [HOLD] Make SmartScanning expense-level thread less confusing[/+] on Apr 18, 2024
  4. dannymcclain commented on Apr 22, 2024

    @dannymcclain
    Contributor

    Here's a mock showing the UI with the updates:

    image

    Note

    The scanning "next steps" are being updated as part of this issue—no need to worry about that here
    CleanShot 2024-04-22 at 10 30 20@2x
    CleanShot 2024-04-22 at 10 30 38@2x

  5. changed the title [-]CRITICAL: [Track expense] [HOLD] Make SmartScanning expense-level thread less confusing[/-] [+]CRITICAL: [Track expense] Make SmartScanning expense-level thread less confusing[/+] on Apr 23, 2024
  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    ImprovementItem broken or needs improvement.
    and removed on Apr 23, 2024
  7. changed the title [-]CRITICAL: [Track expense] Make SmartScanning expense-level thread less confusing[/-] [+][$250] CRITICAL: [Track expense] Make SmartScanning expense-level thread less confusing[/+] on Apr 23, 2024
  8. melvin-bot commented on Apr 23, 2024

    @melvin-bot
  9. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Apr 23, 2024
  10. 32 remaining items

  11. JmillsExpensify commented on May 12, 2024

    @JmillsExpensify
    Contributor

    Payment summary:

    Note that this issue was created after the new pricing tiers went into effect. @fedirjh I also think we need to add a regression test for this issue, since the behavior of the app has changed. Do you mind suggesting one?

  12. Nodebrute commented on May 12, 2024

    @Nodebrute
    Contributor

    @JmillsExpensify this is a critical issue.

  13. JmillsExpensify commented on May 12, 2024

    @JmillsExpensify
    Contributor

    I understand, though it was a simple change.

  14. Nodebrute commented on May 12, 2024

    @Nodebrute
    Contributor

    As per this announcement, critical bugs are valued at $500

  15. JmillsExpensify commented on May 12, 2024

    @JmillsExpensify
    Contributor

    @mallenexpensify this isn't the first time I've seen confusion around CRITICAL issues. Can you chime in to help clear this up. I think we also probably need to consider another announcement for clarity.

  16. fedirjh commented on May 13, 2024

    @fedirjh
    Contributor

    Regression Test Proposal

    1. Launch the app
    2. Tap on the FAB (Floating Action Button) and select 'Track Expense'
    3. Initiate a new scan request
    4. Access the scan request you just created
    5. While the request is being scanned, ensure that:
       - The header shows 'Scan in progress...'
       - The 'Amount' and 'Merchant' fields display 'Scanning...'
    
    • Do we agree 👍 or 👎
  17. JmillsExpensify commented on May 14, 2024

    @JmillsExpensify
    Contributor

    Thanks for your patience on this issue. Everyone has been paid out based on the summary above, and @mallenexpensify expects to circle back on this later this week.

  18. JmillsExpensify commented on May 20, 2024

    @JmillsExpensify
    Contributor

    Circling back on this issue, I'm going to issue new Upwork contracts for the remaining $250 for each of C and C+. So $500 in total. We'll clarify our HIGH//CRITICAL process separately. Thanks everyone for their patience.

  19. melvin-bot commented on May 20, 2024

    @melvin-bot

    @JmillsExpensify, @marcochavezf, @fedirjh, @Nodebrute Huh... This is 4 days overdue. Who can take care of this?

  20. JmillsExpensify commented on May 20, 2024

    @JmillsExpensify
    Contributor

    All Contributors paid $500 in total, so closing this issue out!

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 productionDailyKSv2ExternalAdded to denote the issue can be worked on by a contributorImprovementItem broken or needs improvement.

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions