Skip to content

[Due for payment 2026-10-30] Payment issue for E/App PR#104075 #104875

Open

Description

@melvin-bot

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

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 Oct 23, 2026

    @melvin-bot
    Author

    @ahmedGaber93 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 Contributor+ 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 Oct 26, 2026

    @melvin-bot
    Author

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

  3. melvin-bot commented on Oct 28, 2026

    @melvin-bot
    Author

    @ahmedGaber93 Eep! 4 days overdue now. Issues have feelings too...

  4. melvin-bot commented on Oct 29, 2026

    @melvin-bot
    Author

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  5. melvin-bot commented on Oct 29, 2026

    @melvin-bot
    Author

    Payment Summary

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  6. ahmedGaber93 commented on Oct 30, 2026

    @ahmedGaber93
    Contributor

    Contributor+ 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. new feature.
      Link to the comment on the Issue: N/A. new feature.

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

    • Go to Settings → Troubleshoot → Beta overrides.
    • Enable insightsPage.

    Test:

    1. Create an expense dated in the next month.
    2. Open the Insights tab.
    3. Set the Date filter to a custom range covering the past few months through the next two months.
    4. Set Group by to Month.
    5. Verify Spend over time draws a solid line up to last month, then a dashed line through the current month and every later month.
    6. Hover the current month and verify the tooltip says "so far" and the dot is hollow.
    7. Hover the later month and verify the tooltip shows its month name and the dot is hollow.

    Do we agree 👍 or 👎

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