Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HOLD for payment 2024-11-18] Reports with "report not found" error cause Inbox tab RBR #51488

Open
puneetlath opened this issue Oct 25, 2024 · 14 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Weekly KSv2

Comments

@puneetlath
Copy link
Contributor

puneetlath commented Oct 25, 2024

Reports that have the "Report not found" error in Onyx are not shown in the LHN. But they do cause an RBR to be shown on the Inbox tab. We should align the RBR behavior on the Inbox tab with reports that are shown in the LHN. If a report isn't shown in the LHN, it should never trigger an RBR/GBR on the tab.

cc @pac-guerreiro

Issue OwnerCurrent Issue Owner: @puneetlath
@puneetlath puneetlath added the Bug Something is broken. Auto assigns a BugZero manager. label Oct 25, 2024
@puneetlath puneetlath self-assigned this Oct 25, 2024
Copy link

melvin-bot bot commented Oct 25, 2024

Current assignee @puneetlath is eligible for the Bug assigner, not assigning anyone new.

Copy link

melvin-bot bot commented Oct 28, 2024

@puneetlath Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@pac-guerreiro
Copy link
Contributor

Hi! I’m Pedro Guerreiro from Callstack - expert contributor group. I’d like to work on this task!

@DylanDylann
Copy link
Contributor

From #51425 (comment), On LHN, we use useReportIDs hook to filter and sort reports first

const {orderedReportIDs, currentReportID, policyMemberAccountIDs} = useReportIDs();

I think we should apply the logic in useReportIDs into getChatTabBrickRoadReport to make it consistent

@pac-guerreiro
Copy link
Contributor

@DylanDylann Thanks for the help here!

@puneetlath PR is ready to be reviewed

@pac-guerreiro
Copy link
Contributor

@puneetlath today I applied @DylanDylann suggestions to the PR

@pac-guerreiro
Copy link
Contributor

@puneetlath The PR is ready to be merged! Thanks @DylanDylann 😄

@pac-guerreiro
Copy link
Contributor

@puneetlath the PR is waiting to be merged

Copy link

melvin-bot bot commented Nov 6, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@pac-guerreiro
Copy link
Contributor

The PR is finally merged 🎉 Thanks @puneetlath 😄

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Nov 11, 2024
@melvin-bot melvin-bot bot changed the title Reports with "report not found" error cause Inbox tab RBR [HOLD for payment 2024-11-18] Reports with "report not found" error cause Inbox tab RBR Nov 11, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Nov 11, 2024
Copy link

melvin-bot bot commented Nov 11, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Nov 11, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.59-3 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-11-18. 🎊

For reference, here are some details about the assignees on this issue:

Copy link

melvin-bot bot commented Nov 11, 2024

@DylanDylann @puneetlath 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]

@DylanDylann
Copy link
Contributor

DylanDylann commented Nov 15, 2024

The regression test is included here. So we don't need the checklist here anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Weekly KSv2
Projects
None yet
Development

No branches or pull requests

3 participants