Skip to content

[Due for payment 2026-07-01] Payment issue for E/App PR#91933 #94493

Closed

Description

@melvin-bot

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

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 24, 2026

    @melvin-bot
    Author

    @brunovjk 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]. If no checklist is needed for this issue, you can click: [no checklist button]

  2. melvin-bot commented on Jun 29, 2026

    @melvin-bot
    Author

    @brunovjk Huh... This is 4 days overdue. Who can take care of this?

  3. melvin-bot commented on Jun 30, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  4. melvin-bot commented on Jun 30, 2026

    @melvin-bot
    Author

    Payment Summary

    Upwork Job

    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
  5. brunovjk commented on Jul 1, 2026

    @brunovjk
    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: Not a 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

    Test:

    1. Go to a workspace > Company Cards > Add Cards > Import transactions from File. Use this file:
      Expensify upload (2).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-4483-a2eb-b009-9b9b9a747634
  6. mallenexpensify commented on Jul 2, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @brunovjk due $250 via NewDot

    ^ Test case created. Thx

  7. laurenreidexpensify commented on Jul 3, 2026

    @laurenreidexpensify
    Contributor

    $250 Approved for @brunovjk

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