Skip to content

[Due for payment 2026-04-20] Payment issue for E/App PR#86818 #87793

Closed

Description

@melvin-bot

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

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. added
    InternalRequires API changes or must be handled by Expensify staff
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Apr 13, 2026
  2. melvin-bot commented on Apr 13, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  3. melvin-bot commented on Apr 20, 2026

    @melvin-bot
    Author

    Payment Summary

    Upwork Job

    • Reviewer: @suneox owed $250 via NewDot

    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. mallenexpensify commented on Apr 21, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @suneox due $250 via NewDot

    @suneox plz complete the BZ checklist and tag me in a post once you have. Thx
    (from the deets in the PR, we're going to start adding these soon, I just need to update the process)

  5. suneox commented on Apr 24, 2026

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

      This is a new feature update for backward compatibility with Expensify Classic, changing AttendeeTrackingEnabled to default to true.

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

    Regression Test Proposal

    Precondition:

    Test:

    1. Create a WS Control policy in OldDot
    2. Open the WS in NewDot → Workspace Settings → Rules
    3. Enable rule at More feature -> rules
    4. Navigate to rules setting
    5. Verify the "Attendee Tracking" toggle shows as enabled
    6. Go to WS setting -> Category -> Open any category -> Required fields
    7. Verify the "Require attendees" toggle shown as disabled
    8. Enable "Require attendees"
    9. Create an expense with that category at step 6 (do not add any attendees)
    10. Verify the violation message shows at Attendees field

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-2cc9-a531-453d-d3d448bc2334
  6. suneox commented on Apr 24, 2026

    @suneox
    Contributor

    @mallenexpensify I've completed the checklist for the internal issue.

  7. garrettmknight commented on Apr 27, 2026

    @garrettmknight
    Contributor

    $250 approved for @suneox

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