-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$250] [HOLD for payment 2024-08-01] Group name - RBR doesn't disappear from LHN after removing error message #42765
Comments
Triggered auto assignment to @danieldoglas ( |
👋 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:
|
@danieldoglas FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #vip-vsp |
ProposalPlease re-state the problem that we are trying to solve in this issue.RBR doesn't disappear from LHN after removing error message What is the root cause of that problem?Here we call
and in clearPolicyRoomNameErrors we only clear errorFields but not errorsApp/src/libs/actions/Report.ts Lines 2220 to 2229 in c244fa1
and here when we fail we set errors to common.genericErrorMessageApp/src/libs/actions/Report.ts Lines 665 to 667 in 169a3aa
So the RCA is when "x" is pressed we clear errorFields but not errors What changes do you think we should make in order to solve the problem?Solution 1 App/src/libs/actions/Report.ts Lines 665 to 667 in 169a3aa
Note:we can keep errors here too. What alternative solutions did you explore? (Optional)In App/src/libs/actions/Report.ts Lines 2220 to 2229 in c244fa1
|
Doesn't seem blocker-worthy to me. Let's treat as a regular bug. |
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rojiphil ( |
Triggered auto assignment to @muttmuure ( |
Catching up from OOO |
Not overdue |
@rojiphil bump |
@muttmuure Completed BZ checklist. |
@rojiphil, @danieldoglas, @mountiny, @muttmuure, @Nodebrute Eep! 4 days overdue now. Issues have feelings too... |
Triggered auto assignment to @mallenexpensify ( |
@mallenexpensify can you please take care of the payment on this one? Thanks! |
Job added to Upwork: https://www.upwork.com/jobs/~01f34a445311dae423 |
Current assignee @rojiphil is eligible for the External assigner, not assigning anyone new. |
@rojiphil @Nodebrute , can you please accept the job and reply here once you have? |
@mallenexpensify I haven’t received the Upwork offer yet. Can you send the contract manually when you get a chance? |
Musta forgot to invite ¯_(ツ)_/¯, plz accept meow 🐱 |
@mallenexpensify thank you, accepted. |
@mallenexpensify Accepted offer. Thanks. |
payment in progress |
Contributor: @Nodebrute paid $250 via Upwork @rojiphil do we want a regression test for this? If not, why not? Thx |
@mallenexpensify As mentioned in BZ checklist here, I think we can skip the regression test as this is an edge case. |
@rojiphil , it looks like you just checked the box there. We also want reasoning if we don't create a test case. We want to err on the side of creating more test cases because the QA will know if it's needed. They also have a separate monthly test for edge cases. I created a test case using the steps in the PR |
@mallenexpensify Ok. Got it and noted too. Thanks. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.77-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Issue found when executing PR #41826
Action Performed:
Expected Result:
RBR on LHN gets removed from LHN as well
Actual Result:
RBR stays on LHN even after removing error message
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6495078_1716985565573.bandicam_2024-05-29_15-20-11-422.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @rojiphilThe text was updated successfully, but these errors were encountered: