Skip to content

[Due for payment 2026-06-04] Payment issue for E/App PR#91936 #92018

Closed

Description

@melvin-bot

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

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 May 28, 2026

    @melvin-bot
    Author

    @huult 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. huult commented on May 29, 2026

    @huult
    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.

    The backend expects the header, but we are not passing it.

    • [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: N/A

    • [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/645642

    Regression Test Proposal

    Precondition:

    Test:

    1. Go to a workspace > Company Cards > Add Cards > Import transactions from File. You can use this file: w_9f67f19202de1b258cd1bcd3470527338782cf2f.csv
    2. Follow the import process
    3. Confirm the card displays properly. It may take a bit for it to show.

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-d755-a148-0271-e25a2428adb4
  3. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on May 29, 2026
  4. melvin-bot commented on Jun 3, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  5. melvin-bot commented on Jun 3, 2026

    @melvin-bot
    Author

    Payment Summary

    Upwork Job

    • Reviewer: @huult 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
  6. mallenexpensify commented on Jun 5, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @huult due $250 via NewDot

    ^ Test case created. Thx

  7. JmillsExpensify commented on Jun 29, 2026

    @JmillsExpensify
    Contributor

    $250 approved for @huult

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