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-01-15] [$125] [Pending / Scanning] If multiple receipts are scanning in a report, update the copy of the preview component to be plural (i.e. "receipts scanning") #49054
changed the title [-][Pending / Scanning] If multiple receipts are scanning in a report, update the copy of the preview component to be plural (i.e. "receipts scanning")[/-][+][$125] [Pending / Scanning] If multiple receipts are scanning in a report, update the copy of the preview component to be plural (i.e. "receipts scanning")[/+]on Sep 12, 2024
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 (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[@eh2077] 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:
[@eh2077 ] 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:
[@eh2077 ] 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 Template
[@isabelastisser ] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
[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.
No, we don't need to add regression test here because the fix is straightforward.
Activity
melvin-bot commentedon Sep 12, 2024
Triggered auto assignment to @isabelastisser (
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.melvin-bot commentedon Sep 12, 2024
Triggered auto assignment to @kadiealexander (
NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.[-][Pending / Scanning] If multiple receipts are scanning in a report, update the copy of the preview component to be plural (i.e. "receipts scanning")[/-][+][$125] [Pending / Scanning] If multiple receipts are scanning in a report, update the copy of the preview component to be plural (i.e. "receipts scanning")[/+]melvin-bot commentedon Sep 12, 2024
trjExpensify commentedon Sep 12, 2024
Should be a simple task.
108 remaining items
MariaHCD commentedon Jan 14, 2025
Not overdue - we just need the BZ checklist to move forward here
isabelastisser commentedon Jan 14, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[@eh2077] 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:
[@eh2077 ] 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:
[@eh2077 ] 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 Template
[@isabelastisser ] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
isabelastisser commentedon Jan 14, 2025
@eh2077, please complete the checklist before the payment can be processed. Thanks!
isabelastisser commentedon Jan 15, 2025
Bump @eh2077 to complete the checklist. Thanks!
eh2077 commentedon Jan 16, 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: https://github.com/Expensify/App/pull/24235/files#r1918697408
[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.
No, we don't need to add regression test here because the fix is straightforward.
eh2077 commentedon Jan 16, 2025
@isabelastisser Done, thanks for the ping!
isabelastisser commentedon Jan 16, 2025
Payment summary:
@nyomanjyotisa automatic offer (Contributor) $125 - paid in Upwork.
@eh2077 requires payment through NewDot Manual Requests C+ $125
pendingshubham1206agra commentedon Jan 16, 2025
@isabelastisser The issue is marked for $125. Can you double-check the payment summary?
isabelastisser commentedon Jan 17, 2025
@shubham1206agra, my confusion, sorry! updated!
JmillsExpensify commentedon Jan 22, 2025
$125 approved for @eh2077