Skip to content

[Due for payment 2026-11-02] Payment issue for E/App PR#104372 #105062

Closed

Description

@melvin-bot

Issue created to compensate the Contributor+ member for their work on #104372
E/E issue linked to the PR - https://www.github.com/Expensify/Expensify/issues/689351.
Contributor+ member who reviewed the PR - @Ollyws.

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

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. melvin-bot commented on Oct 26, 2026

    @melvin-bot
    Author

    @Ollyws The PR you reviewed has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

  2. melvin-bot commented on Oct 29, 2026

    @melvin-bot
    Author

    @Ollyws Whoops! This issue is 2 days overdue. Let's get this updated quick!

  3. melvin-bot commented on Nov 1, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  4. melvin-bot commented on Nov 1, 2026

    @melvin-bot
    Author

    Payment Summary

    • Reviewer: @Ollyws owed $175 via NewDot

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  5. melvin-bot commented on Nov 5, 2026

    @melvin-bot
    Author

    @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  6. melvin-bot commented on Nov 5, 2026

    @melvin-bot
    Author

    @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  7. melvin-bot commented on Nov 5, 2026

    @melvin-bot
    Author

    @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  8. Ollyws commented on Nov 5, 2026

    @Ollyws
    Contributor

    Contributor+ Checklist:

    • [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to the comment on the PR: N/A, upstream bug
      Link to the comment on the Issue:

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal Template. Needed for all bugs AND new features

    Regression Test Proposal

    Precondition:

    Test:

    1. Open Personal information under profile settings.
    2. Complete the other required fields with valid test data of US address.
    3. In the phone field, enter 9833330123.
    4. Press Save, and verify/confirm the form advances without a phone-number validation error.
    5. Repeat steps 2–3 with +19833330123 and +1-(983)-333-0123; verify both formats are accepted.
    6. Repeat steps 2–3 with +11234567890; verify an invalid-phone-number error blocks progress.
    

    Do we agree 👍 or 👎

  9. mallenexpensify commented on Nov 6, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @Ollyws due $175 via NewDot

  10. flaviadefaria commented on Nov 9, 2026

    @flaviadefaria
    Contributor

    Approved: @Ollyws due $175 via NewDot

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 productionDailyKSv2Task

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions