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-09-02] [$250] [HELP PANEL] Update the logic and fix help panel appearing without NVP #68462
changed the title [-][HELP PANEL] Update the logic and fix help panel appearing without NVP[/-][+][$250] [HELP PANEL] Update the logic and fix help panel appearing without NVP[/+]on Aug 21, 2025
changed the title [-][$250] [HELP PANEL] Update the logic and fix help panel appearing without NVP[/-][+][Due for payment 2025-09-02] [$250] [HELP PANEL] Update the logic and fix help panel appearing without NVP[/+]on Aug 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.98-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dominictb@lydiabarclay 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: Help content update
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: Help content update
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: NA. Help content update.
[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: NA
[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.
Activity
melvin-bot commentedon Aug 20, 2025
Triggered auto assignment to @Beamanator, see https://stackoverflow.com/c/expensify/questions/7972 for more details.
[-][HELP PANEL] Update the logic and fix help panel appearing without NVP[/-][+][$250] [HELP PANEL] Update the logic and fix help panel appearing without NVP[/+]melvin-bot commentedon Aug 21, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021958443488218896064
melvin-bot commentedon Aug 21, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (
External)18 remaining items
[-][$250] [HELP PANEL] Update the logic and fix help panel appearing without NVP[/-][+][Due for payment 2025-09-02] [$250] [HELP PANEL] Update the logic and fix help panel appearing without NVP[/+]melvin-bot commentedon Aug 26, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.98-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-09-02. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Aug 26, 2025
@dominictb @lydiabarclay 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]
lydiabarclay commentedon Aug 29, 2025
@dominictb could you fill out the BZ checklist before 9/2? Tysm! I will be out for the long weekend so wanted to make sure I pinged before that date.
lydiabarclay commentedon Sep 2, 2025
Payment Summary
Contributor: @blazejkustra does not require payment (Contractor)
Contributor+: @dominictb paid $250 via Upwork
✅ Regression test filed
dominictb commentedon Sep 3, 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: NA. Help content update.
[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: NA
[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: https://github.com/Expensify/Expensify/issues/543442
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎