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 2024-10-25] Debug Mode - "Has RBR" is not shown for report that has RBR in LHN #50403
Version Number: v9.0.46-1 Reproducible in staging?: Y Reproducible in production?: Unable to check Prod. There is no debug option in prod Issue was found when executing this PR:#48442 Email or phone of affected tester (no customers):applausetester+ds@applause.expensifail.com Issue reported by: Applause Internal Team
Action Performed:
Enable "Debug mode" in troubleshoot
On home page, open a chat report from LHN that has a RBR
Click on the header of the chat you just opened, then click on Debug
Expected Result:
On the Details tab, "Has RBR" is shown in "Visible in LHN" for report that has RBR in LHN
Actual Result:
On the Details tab, "Has GBR" is shown instead of "Has RBR" in "Visible in LHN" for report that has RBR in LHN. For reports that has GBR "has GBR" is shown.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
changed the title [-]Debug Mode - "Has RBR" is not shown for report that has RBR in LHN[/-][+][HOLD for payment 2024-10-25] Debug Mode - "Has RBR" is not shown for report that has RBR in LHN[/+]on Oct 18, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.50-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
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:
[@DylanDylann] The PR that introduced the bug has been identified. Link to the PR:
[@DylanDylann] 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:
[@DylanDylann] 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:
[@DylanDylann] Determine if we should create a regression test for this bug.
[@DylanDylann] 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.
[@adelekennedy] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
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:
[@DylanDylann] The PR that introduced the bug has been identified. Link to the PR: #48442
[@DylanDylann] 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: Just discussed with the author
[@DylanDylann] 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: NA
[@DylanDylann] Determine if we should create a regression test for this bug. Yes
[@DylanDylann] 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
Enable Debug mode in troubleshoot
On home page, open a chat report from LHN that has a RBR
Click on the header of the chat you just opened, then click on Debug
On the Details tab, Has RBR is shown in Visible in LHN for report that has RBR in LHN
Activity
melvin-bot commentedon Oct 8, 2024
Triggered auto assignment to @carlosmiceli (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 8, 2024
Triggered auto assignment to @adelekennedy (
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.github-actions commentedon Oct 8, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
15 remaining items
[-]Debug Mode - "Has RBR" is not shown for report that has RBR in LHN[/-][+][HOLD for payment 2024-10-25] Debug Mode - "Has RBR" is not shown for report that has RBR in LHN[/+]melvin-bot commentedon Oct 18, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Oct 18, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.50-8 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 2024-10-25. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Oct 18, 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:
melvin-bot commentedon Oct 25, 2024
Payment Summary
Upwork Job
BugZero Checklist (@adelekennedy)
adelekennedy commentedon Oct 28, 2024
Payouts due:
adelekennedy commentedon Oct 30, 2024
@DylanDylann bump also on the checklist
DylanDylann commentedon Oct 30, 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:
[@DylanDylann] The PR that introduced the bug has been identified. Link to the PR: #48442
[@DylanDylann] 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: Just discussed with the author
[@DylanDylann] 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: NA
[@DylanDylann] Determine if we should create a regression test for this bug. Yes
[@DylanDylann] 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
Do we agree 👍 or 👎
melvin-bot commentedon Nov 4, 2024
@mountiny, @pac-guerreiro, @adelekennedy, @DylanDylann Huh... This is 4 days overdue. Who can take care of this?