[HOLD for payment 2024-10-30] [Debug Mode] Show reason for RBR/GBR on LHN tabs

[puneetlath]

I would like to add a feature to the Debug Mode functionality, where if a user has an RBR or GBR on any of the three LHN tabs -- Inbox, Search, Account Settings -- we tell you what the reason is for that RBR/GBR being there.

For example, in this image, I have an RBR on the Inbox tab. I would like to be able to see what is causing that RBR.

Issue Owner

Current Issue Owner: @puneetlath

[melvin-bot]

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

[melvin-bot]

⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature)

[puneetlath]

@dannymcclain un-assigning you since this is for debug mode, so I don't think there will be any UI considerations. But if there do end up being, I'll assign you back!

[pac-guerreiro]

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

[pac-guerreiro]

@puneetlath I'll open a PR soon for this! 😄

I'm currently working on getting the settings GBR/RBR causes and setting the logic to redirect users to what is triggering those GBR/RBR.

[DylanDylann]

@puneetlath Could I help on this issue? because this may relate to previous PRs on the debug mode feature that I did before

[DylanDylann]

@puneetlath please help confirm if this is what you expected. One more thing, If we have many GBR/RBR on LHN, which report should be prioritized to display on the below of LHN

cc @pac-guerreiro

[puneetlath]

I don't think it matters really in that scenario. Any one of them is fine.

[pac-guerreiro]

Still waiting on final review from @DylanDylann

[pac-guerreiro]

Waiting for someone to confirm translations on expensify-open-source 😄

[pac-guerreiro]

The PR is ready to be merged! Thanks @Gonals for confirming the spanish translations and @DylanDylann for the review 🙌

@puneetlath let me know if you like the final result

[pac-guerreiro]

The PR is finally merged with main 🙌

[melvin-bot]

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

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.52-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [Debug Mode] Show reason for RBR/GBR on LHN tabs #49962

If no regressions arise, payment will be issued on 2024-10-30. 🎊

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

• @pac-guerreiro does not require payment (Contractor)
• @DylanDylann requires payment (Needs manual offer from BZ)

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@DylanDylann] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [@puneetlath] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[melvin-bot]

Payment Summary

Upwork Job

• Contributor: @pac-guerreiro is from an agency-contributor and not due payment
• ROLE: @DylanDylann paid $(AMOUNT) via Upwork (LINK)

BugZero Checklist (@puneetlath)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[puneetlath]

@DylanDylann shall we add a regression test here?

[DylanDylann]

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: NA
[@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: NA
[@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

1. Go to App
2. Open debug mode
3. Verify that LHN shows a green indicator and a message to explain on the bottom if there is any GBR on LHN items or LHN shows a red indicator and a message to explain on the bottom if there is any RBR on LHN.
4. Click on View button on the indicator
5. Navigate to the place that caused RBR/GBR

Do we agree 👍 or 👎

[melvin-bot]

@puneetlath, @pac-guerreiro, @DylanDylann Huh... This is 4 days overdue. Who can take care of this?

[puneetlath]

I'll add this as a milestone to this offer once it has been accepted. @DylanDylann please ping me here when you've accepted it.

[DylanDylann]

@puneetlath Accepted 🙏

[puneetlath]

Paid the milestone.

Regression test here: https://github.com/Expensify/Expensify/issues/442242