Skip to content

[Due for payment 2026-05-28] Payment issue for E/App PR#89744 #91351

Closed

Description

@melvin-bot

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

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 May 21, 2026
  2. melvin-bot commented on May 21, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  3. melvin-bot commented on May 28, 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
  4. mallenexpensify commented on May 29, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @ChavdaSachin due $250 via NewDot

    @ChavdaSachin plz complete the BZ checklist and tag me in a post once you have. Thx

  5. ChavdaSachin commented on May 29, 2026

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

    Feature refinement, no offending PR

    • [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: NA

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

    Regression Test Proposal

    Precondition:

    Test:

    1. Login with an Expensifail account
    2. Start a 1-on-1 DM with Concierge
    3. Send it a message, ex: "How do I export a report?"
    4. Observe that the streamed answer doesn't display an incomplete markdown format

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-1a90-a989-85a1-4149041c3404
  6. ChavdaSachin commented on May 29, 2026

    @ChavdaSachin
    Contributor
  7. quinthar commented on May 30, 2026

    @quinthar
    Contributor

    Approved $250 to @ChavdaSachin

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