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 2025-03-10] [Due for payment 2025-03-05] [HOLD #55006/#55007][Manager McTest] Add the Manager McTest Tooltips/Recipient to Manual/Distance Flow #55009
Validation: User sees Manager as a recipient if they meet Beta/NVP reqs and are in the Manual/Distance/Scan receipt flow. User may see the follow up tooltips if they did not dismiss the main tooltip yet.
changed the title [-][HOLD #55006/#55007][Manager McTest] Implement the new flow for Manual/Distance (add tooltips, submit to ManagerMcTest)[/-][+][HOLD #55006/#55007][Manager McTest] Add the Manager McTest Tooltips/Recipient to Manual/Distance Flow[/+]on Jan 10, 2025
Issue is ready for payment but no BZ is assigned. @laurenreidexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
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:
[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 #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:
[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 Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
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:
[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: New Feature, not a bug
[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:
[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.
[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:
Login in a new account
Open FAB
Select Create Expense (we can select any request type: manual, scan, distance)
When on Scan tab verify that tooltip for trying out testing receipt is visible
Go to select participant page
Verify that Manager McTest is visible and tooltip for selecting it for testing is visible
Select Manager McTest
On confirmation page verify that the tooltip above confirm button is visible
Activity
[-][HOLD #55006/#55007][Manager McTest] Implement the new flow for Manual/Distance (add tooltips, submit to ManagerMcTest)[/-][+][HOLD #55006/#55007][Manager McTest] Add the Manager McTest Tooltips/Recipient to Manual/Distance Flow[/+]JKobrynski commentedon Jan 10, 2025
Hi, I'm Julian from Callstack - expert agency - and I would like to work on this issue.
grgia commentedon Jan 24, 2025
on HOLD
grgia commentedon Feb 6, 2025
Not overdue, on hold
27 remaining items
melvin-bot commentedon Mar 10, 2025
Issue is ready for payment but no BZ is assigned. @laurenreidexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!
melvin-bot commentedon Mar 10, 2025
Payment Summary
Upwork Job
BugZero Checklist (@laurenreidexpensify)
laurenreidexpensify commentedon Mar 11, 2025
@grgia can you you confirm the fee for @DylanDylann - is this $250? Thanks
laurenreidexpensify commentedon Mar 11, 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 #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:
[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 Template
[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
Precondition:
Test:
Do we agree 👍 or 👎
laurenreidexpensify commentedon Mar 11, 2025
@DylanDylann @JKobrynski can we please get this filled out? Thanks!
DylanDylann commentedon Mar 11, 2025
@grgia Do we require the regression test on this issue?
grgia commentedon Mar 11, 2025
@DylanDylann yes for the tooltips part
DylanDylann commentedon Mar 12, 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: New Feature, not a bug
[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:
[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.
[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 👎
laurenreidexpensify commentedon Mar 13, 2025
Payment Summary:
C+ $250 offer sent in Upwork
laurenreidexpensify commentedon Mar 17, 2025
Payment Summary:
C+ $250 paid in Upwork @DylanDylann