Skip to content

[Due for payment 2026-05-20] Payment issue for E/App PR#90358 #90566

Closed

Description

@melvin-bot

Issue created to compensate the Contributor+ member for their work on #90358
E/E issue linked to the PR - no internal issue.
Contributor+ member who reviewed the PR - @abzokhattab.

Wait 7 days after the PR is deployed to production before issuing payment in case there are regressions.

Issue OwnerCurrent Issue Owner: @abzokhattab

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on May 13, 2026
  2. melvin-bot commented on May 13, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  3. melvin-bot commented on May 20, 2026

    @melvin-bot
    Author

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  4. abzokhattab commented on May 23, 2026

    @abzokhattab
    Contributor

    No BugZero checklist needed — this is a performance improvement / refactor (React Compiler compliance), not a bug fix.

  5. abzokhattab commented on May 23, 2026

    @abzokhattab
    Contributor
  6. mallenexpensify commented on May 25, 2026

    @mallenexpensify
    Contributor

    @roryabraham for this performance improvement, there were many regressions. Should they be taken into account for reducing pay? We don't state anywhere, that I know of, that we treat regressions differently for bug vs performance fixes (or, other instances (outside of there maybe being an unwritten consideration for new features being viewed differently))

    Thx

  7. roryabraham commented on May 25, 2026

    @roryabraham
    Contributor

    I personally think we can pay the standard review amount. This PR was so low-level that it had potential to many many different things in the app.

  8. mallenexpensify commented on May 26, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @abzokhattab due $250 via NewDot

  9. quinthar commented on Jun 13, 2026

    @quinthar
    Contributor

    Approved $250 to @abzokhattab

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 productionDailyKSv2InternalRequires API changes or must be handled by Expensify staffTask

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions