You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-11-05] Payment issue for E/App PR#104566 #105416
@ikevin127 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]
[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 - This PR adds a new feature (the Rejected column in Search), so there is no regression and no offending PR.
Link to the comment on the Issue: N/A
[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
As a submitter on a workspace with approvals enabled, submit three reports to an approver.
As the approver, reject one expense on the first report.
As the approver, reject the whole second report.
As the submitter, go to Spend > Expenses.
Click Display > Edit columns.
Verify that Rejected is listed and not selected by default.
Select Rejected and click Save.
Verify that the Rejected column shows Yes for the rejected expense and No for the others.
Click the Rejected column header.
Verify that the rejected expense moves to the top.
Click the Rejected column header again.
Verify that the rejected expense moves to the bottom.
Select all expenses and click Export > Current view.
Verify that the exported file has a Rejected column with Yes for the rejected expense and No for the others.
Go to Spend > Reports and repeat steps 5 to 14.
Verify that the Rejected column, sorting and export show Yes for the second report and No for the first and third reports.
Activity
melvin-bot commentedon Oct 29, 2026
@ikevin127 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]
melvin-bot commentedon Nov 4, 2026
@ikevin127 Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Nov 4, 2026
@ikevin127 Eep! 4 days overdue now. Issues have feelings too...
ikevin127 commentedon Nov 4, 2026
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 - This PR adds a new feature (the Rejected column in Search), so there is no regression and no offending PR.
Link to the comment on the Issue: N/A
[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
Do we agree 👍 or 👎.
melvin-bot commentedon Nov 4, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Nov 4, 2026
@ikevin127 Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Nov 4, 2026
Payment Summary
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Nov 6, 2026
Payment Summary
Contributor+: @ikevin127 due $175 via NewDot
quinthar commentedon Nov 8, 2026
Approved $175 to @ikevin127