Repository navigation
[HOLD for payment 2024-10-10] LHN option and badge #45181
Description
Part of the Invoicing payments project
Main issue: https://github.com/Expensify/Expensify/issues/382977
Doc section: https://docs.google.com/document/d/1CF5gw-SJx7ckZCgTJNj1IqBnsRuSxD2Bfd_uB5rRGxk/edit#heading=h.yv8t9d8vscvw
Project: [#whatsnext] #billpay (view)
Activity
VickyStash commentedon Jul 22, 2024
Hi, I'm Viktoryia from Callstack - expert contributor group - and I would like to work on this issue.
VickyStash commentedon Jul 25, 2024
Note: Later phase of implementation
madmax330 commentedon Sep 2, 2024
This is waiting on some backend and front-end before it can be started
rezkiy37 commentedon Sep 26, 2024
Hi, I am Michael (Mykhailo) from Callstack, an expert agency and I can work on this issue.
7 remaining items
melvin-bot commentedon Oct 10, 2024
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
melvin-bot commentedon Oct 14, 2024
Triggered auto assignment to @dylanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.madmax330 commentedon Oct 14, 2024
@dylanexpensify can you just make the payment for @getusha for the PR Review here?
dylanexpensify commentedon Oct 14, 2024
On it!
Payment summary:
Contributor+: @getusha $250
Please apply/request!
getusha commentedon Oct 28, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@getusha] The PR that introduced the bug has been identified. Link to the PR: N/a this was a new feature
[@getusha] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/a this was a new feature
[@getusha] A discussion in #expensify-bugs 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:
[@getusha] Determine if we should create a regression test for this bug. Yes
[@getusha] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
Regression Test Proposal
More features> More featuresDo we agree 👍 or 👎
garrettmknight commentedon Oct 29, 2024
$250 approved for @getusha