-
Notifications
You must be signed in to change notification settings - Fork 4
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
BUG - sev-3 - All - Claims: 'info needed' label persists until logout for claims with decision requested/5103 submitted #9902
Comments
@TKDickson is a log out required or does it fix itself if you back out of the list screen to the benefits category landing screen and go back into claims? If it's the latter then it's that we aren't updating the query correctly manually for the list view to refresh itself. |
@Sparowhawk I was only seeing it on logout. I did exit the list page and come back in again -- but I don't remember if it was going all the way out to the benefits landing screen, or if it was just the 'claims history' and 'claims letters' menu page, when I was checking the 'leave and come back' workflow. Would that make a difference either way? |
No it would not make a difference as long as you backed out one screen in the navigation and then reentered the list. This may be a BE data not updated yet issue |
12/11/2024 - @kellylein @timwright12 @oddballpete @Eallan919 @ATeal @TKDickson The MFS team will be taking this ticket into Sprint 7, (12/14/2024-12/27/2024) |
12/11/2024 - Therese added video per Matt's request, this is in progress now. |
12/12/2024 - this was blocked because of an access issue. Convo in Slack, need to review this behind a feature flag. Matt is continuing with his testing. “Short explanation is that if they're flipping that feature flag relatively soon (which it sounds like they will), then the bug will likely no longer be relevant/happen in the app. I'd mark it as paused/blocked until that's resolved" Moving this ticket out of Sprint 6 and into Blocked until we have confirmed that the FF has been flipped. |
I manually flipped the feature flag to test locally (submitEvidenceExpansion flag in remoteConfig) and documented the process from the original video. I'd also like to point out this comment thread in the DSVA slack channel that is relevant to this issue as there was a lot of discussion there. More specifically, Jacob expressed some concern about the ticket. I figured I'd mention this so we can best determine how to move forward. Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-01-02.at.14.55.54.mp4 |
@matt-guest-wilcore did you have a chance to review the FF code? |
@jennb33 not yet but will make time today to look at it. |
I reviewed the video I posted earlier and if you pay attention to end of the video and note the claim data it looks like the claim is updated and the tag is removed (the video shows another claim with the 'more info' tag). It looks like the feature flag code fixes this issue. To be absolutely sure, it'd be nice to have a staging account preloaded with 5103 data to test and confirm further. |
What happened?
During the same session that you submit a 5103/request a decision on a claim, they'll still display in the claims history list as "more info requested" (if you can't access that video link, try the file in the screenshots section below). Which is somewhat alarming, because you go to the claim details and don't have the opportunity to submit anything.
Logging out and back in again, we'll correctly remove the label from the claim in the claims history list.
Specs:
Steps to Reproduce
Desired behavior
Acceptance Criteria
Bug Severity - BE SURE TO ADD THE SEVERITY LABEL
See Bug Tracking for details on severity levels
Linked to Story
Screen shot(s) and additional information
ScreenRecording_10-16-2024.09-40-40_1.MP4
Full JSON response for services related to issue (expand/collapse)
Ticket Checklist
The text was updated successfully, but these errors were encountered: