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
Expected behavior
Each Coverage ID + Subscriber ID combination should be unique, ensuring no duplicate records appear in the dropdown
Screenshots
Desktop (please complete the following information):
OS: [windows]
Browser [chrome]
Version [132.0.6834.111]
Additional context
Add any other context about the problem here.
🚨 DO NOT EDIT BELOW THIS LINE 🚨
Instructions for Requesting Assignment:
To request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:
Describe your solution clearly:
Provide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.
Expected Timeline:
End date: [Expected submission date of a completed Pull Request]
Additional Context:
Include any other relevant context, links, screenshots, or resources that support your proposed solution.
🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.
The text was updated successfully, but these errors were encountered:
Describe the bug
The dropdown displays duplicate coverage records where the same Coverage ID and Subscriber ID appear multiple times
To Reproduce
Steps to reproduce the behavior:
Click here to reproduce
See error
Expected behavior
Each Coverage ID + Subscriber ID combination should be unique, ensuring no duplicate records appear in the dropdown
Screenshots
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
🚨 DO NOT EDIT BELOW THIS LINE 🚨
Instructions for Requesting Assignment:
To request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:
Describe your solution clearly:
Provide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.
Expected Timeline:
Additional Context:
Include any other relevant context, links, screenshots, or resources that support your proposed solution.
The text was updated successfully, but these errors were encountered: