Skip to content

[Due for payment 2026-06-18] Payment issue for E/App PR#92297 #93347

Closed

Description

@melvin-bot

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

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 Jun 11, 2026

    @melvin-bot
    Author

    @daledah 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 BugZero 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]

  2. melvin-bot commented on Jun 15, 2026

    @melvin-bot
    Author

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

  3. daledah commented on Jun 17, 2026

    @daledah
    Contributor

    BugZero 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 refactor
      Link to the comment on the Issue: N/A refactor

    • [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.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/650516

    Regression Test Proposal

    Precondition: account with several reports ready for payment

    Test:

    1. Navigate to Spend
    2. Select the reports ready for payment
    3. Pay the reports
    4. Verify that it works.

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-b3f2-ab52-cc97-a0e9fbcd64b4
  4. daledah commented on Jun 17, 2026

    @daledah
    Contributor

    @luacmartins may I request an increase in the bounty for this issue? The PR involved a large number of changes across 19 files. This added considerable extra effort to the review and testing process across all platforms

    Proposed amount to increase the price to: 500

    Multiple PRs - Link to all PRs

    Main PR: #92297
    Follow up PR: #93308

  5. luacmartins commented on Jun 17, 2026

    @luacmartins
    Contributor

    I think that one was pretty standard, so the regular bounty seems fair in this case.

  6. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jun 17, 2026
  7. melvin-bot commented on Jun 17, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  8. melvin-bot commented on Jun 17, 2026

    @melvin-bot
    Author

    Payment Summary

    Upwork Job

    • Reviewer: @daledah owed $250 via NewDot

    BugZero Checklist (@mallenexpensify)

    • 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
  9. mallenexpensify commented on Jun 19, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @daledah due $250 via NewDot

    ^ Test case created. Thx

    Working off

    I think that one was pretty standard, so the regular bounty seems fair in this case.

    and not taking into account

    Deploy Blocker #93230 was identified to be related to this PR.

  10. quinthar commented on Jul 31, 2026

    @quinthar
    Contributor

    Approved $250 to @daledah

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