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
[HOLD for payment 2025-02-04] [$250] Delete Receipt button is not displayed in merged transaction #53922
Not familiar with this flow, but seems like this bug came from an applause issue where we asked them to create regression tests, so I'm thinking this is in fact a bug
changed the title [-]Delete Receipt button is not displayed in merged transaction[/-][+][$250] Delete Receipt button is not displayed in merged transaction[/+]on Dec 12, 2024
@joekaufmanexpensify@jliexpensify Hi there! This issue came up when I was writing tests for the merge transaction feature. I checked the behavior on OD and in ND and it seems ND is missing the detach receipt/delete receipt option. Had a discussion with @trjExpensify and @mountiny around this and seems it's either a missing feature or a bug.
@dukenv0307 / @dominictb@jliexpensify@dukenv0307 / @dominictb The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production
2b. Reported on staging (deploy blocker)
2c. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] 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:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in https://app.slack.com/client/E047TPA624F/C01GTK53T8Q 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.
Activity
melvin-bot commentedon Dec 11, 2024
Triggered auto assignment to @jliexpensify (
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.jliexpensify commentedon Dec 12, 2024
@joekaufmanexpensify @robertjchen @luacmartins hello - would this be a new feature? Is there a C+ that's currently working on this?
joekaufmanexpensify commentedon Dec 12, 2024
Not familiar with this flow, but seems like this bug came from an applause issue where we asked them to create regression tests, so I'm thinking this is in fact a bug
[-]Delete Receipt button is not displayed in merged transaction[/-][+][$250] Delete Receipt button is not displayed in merged transaction[/+]melvin-bot commentedon Dec 12, 2024
Job added to Upwork: https://www.upwork.com/jobs/~021867328664713695509
melvin-bot commentedon Dec 12, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @dominictb (
External)jliexpensify commentedon Dec 12, 2024
Thanks Joe!
isagoico commentedon Dec 13, 2024
@joekaufmanexpensify @jliexpensify Hi there! This issue came up when I was writing tests for the merge transaction feature. I checked the behavior on OD and in ND and it seems ND is missing the detach receipt/delete receipt option. Had a discussion with @trjExpensify and @mountiny around this and seems it's either a missing feature or a bug.
joekaufmanexpensify commentedon Dec 13, 2024
Cool. TY!
76 remaining items
melvin-bot commentedon Jan 28, 2025
@dukenv0307 / @dominictb @jliexpensify @dukenv0307 / @dominictb The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]
dukenv0307 commentedon Jan 29, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] 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:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in https://app.slack.com/client/E047TPA624F/C01GTK53T8Q 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 https://github.com/Expensify/App/blob/main/contributingGuides/REGRESSION_TEST_BEST_PRACTICES.md steps using the template below to ensure the same bug will not reach production again. Yes
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
jliexpensify commentedon Feb 4, 2025
Payment Summary
jliexpensify commentedon Feb 4, 2025
@dominictb the previous Upworks job closed, can you accept this one? https://www.upwork.com/jobs/~021886615380373019169
Thanks!
jliexpensify commentedon Feb 5, 2025
Bumping @dominictb to accept in Upworks so I can pay + close!
dominictb commentedon Feb 5, 2025
@jliexpensify Accepted, thank you 🙇
jliexpensify commentedon Feb 5, 2025
Paid and job closed.
@dukenv0307 please refer to this summary.
JmillsExpensify commentedon Feb 20, 2025
$250 approved for @dukenv0307