Skip to content

[CFI] [$500] Add Crop receipt to NewDot #79961

Closed

Description

@trjExpensify

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: v9.3.3-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from BrowserStack: N/A
**Expensify/Expensify Issue URL:**https://github.com/Expensify/Expensify/issues/576875
Issue reported by: multiple migrated customers incl. @twisterdotcom's escalation cited below
Slack conversation: #migrate

Action Performed:

  1. Go to global create > Create expense
  2. Scan a receipt
  3. Click on the receipt preview

Expected Result:

This is a new feature we're bringing across from Classic.

  1. Add the Rotate Crop Replace buttons beneath the image, leaving icons for Download and Delete in the top bar:
Image
  1. When clicking Crop, replace the three buttons with two buttons to Cancel or Save. Reveal a draggable border around the receip preview:
Image
  1. Allow all four corners and sides of the draggable border to be dragged to crop to the desired size:
Image
  1. Clicking Save exits the crop mode and resizes the receipt preview accordingly (or Cancel to exit without any changes):
Image

Actual Result:

This feature doesn't exist on NewDot currently.

Workaround:

Switch to Classic to use this feature.

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

Screenshots/Videos

In-line above.

View all open jobs on GitHub
t

Upwork Automation - Do Not Edit
Issue Owner

Current Issue Owner: @dukenv0307

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    NewFeatureSomething to build that is a new item.
    on Jan 20, 2026
  2. melvin-bot commented on Jan 20, 2026

    @melvin-bot
  3. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jan 20, 2026
  4. melvin-bot commented on Jan 20, 2026

    @melvin-bot

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

  5. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 (External)

  6. melvin-bot commented on Jan 20, 2026

    @melvin-bot

    Current assignee @dannymcclain is eligible for the NewFeature assigner, not assigning anyone new.

  7. 23 remaining items

  8. melvin-bot commented on Feb 20, 2026

    @melvin-bot

    @dukenv0307 Eep! 4 days overdue now. Issues have feelings too...

  9. dubielzyk-expensify commented on Feb 22, 2026

    @dubielzyk-expensify
    Contributor

    What's happening with this issue?

  10. nkdengineer commented on Feb 23, 2026

    @nkdengineer
    Contributor

    @dubielzyk-expensify We're still figuring out the icon problem here

  11. melvin-bot commented on Feb 27, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  12. melvin-bot commented on Feb 27, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  13. melvin-bot commented on Feb 28, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

  14. nkdengineer commented on Mar 12, 2026

    @nkdengineer
    Contributor

    @trjExpensify The PR was deployed to production a week ago. We're good to go with payment now.

    We have some regressions that I have handled, and we CPed without reverting the PR. Since it's a new complex feature, it would be greatly appreciated if the regression penalty could be exempted

  15. trjExpensify commented on Mar 12, 2026

    @trjExpensify
    ContributorAuthor

    The regression period applies from when the code is merged.

    Payment summary as follows:

    Go ahead and request!

  16. quinthar commented on Mar 18, 2026

    @quinthar
    Contributor

    Approved $250 to @dukenv0307

  17. twisterdotcom commented on Mar 19, 2026

    @twisterdotcom
    Contributor

    @nkdengineer has submitted payment for this report on ND here.

    SO: https://stackoverflowteams.com/c/expensify/questions/7582

    Zapier Logs Run ID: 00040eee-2779-aa77-add9-6737a136d724
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

ExternalAdded to denote the issue can be worked on by a contributorNewFeatureSomething to build that is a new item.ReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions