\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13711,"Password input fields missing autocomplete attributes","2025-10-01T07:27:03Z","https://github.com/ohcnetwork/care_fe/issues/13711",0.6955982,{"description":3227,"labels":3228,"number":3229,"owner":3172,"repository":3173,"state":3183,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**Describe the bug**\nWhen adding a user exception, the validation error message does not clear immediately after the user checks the checkbox , but the form is submitted.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Users → Click \"Add Exception\"\n2. Observe that the error messages persists after checking the checkbox.\n\nhttps://github.com/user-attachments/assets/90cc5bcc-3fe6-4ac1-b313-59540bccb70b\n\n\n**Expected behavior**\nThe error message should disappear as the user checks the checkbox.\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],12803,"Validation Message Fails to Clear on Checkbox Toggle","2025-07-16T12:13:25Z","https://github.com/ohcnetwork/care_fe/issues/12803",0.6997845,{"description":3235,"labels":3236,"number":3239,"owner":3172,"repository":3173,"state":3183,"title":3240,"updated_at":3241,"url":3242,"score":3243},"**Describe the bug**\nIn the Charge Definition Form, the `derived_from_uri` field is optional. However, if a user accidently focuses the field or leaves it empty (after typing and clearing), the form throws a \"Invalid URL\" error on submit.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Charge Item Definitions'\n2. Click on 'Add Definition' or 'Edit' button\n3. Click on 'Derived from URI' field and leave it empty\n4. Attempt to submit the form\n5. See error\n\n**Expected behavior**\nThe form should allow submission if the field is empty, regardless of whether it was focused or modified.\n\n**Screenshots**\n\n\u003Cimg width=\"1898\" height=\"905\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3bc6abac-1214-4f86-a958-0fb372c236b0\" />\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3237,3238],{"name":3200,"color":3201},{"name":3203,"color":3204},13261,"Optional `derived_from_uri` field triggers validation error","2025-08-06T05:56:29Z","https://github.com/ohcnetwork/care_fe/issues/13261",0.70394176,{"description":3245,"labels":3246,"number":3247,"owner":3172,"repository":3173,"state":3183,"title":3248,"updated_at":3249,"url":3250,"score":3251},"**Describe the bug**\nIn the **Patient Create Form**, the following required fields:\n- Name\n- Current Address \n- Permanent Address\n\nare accepting whitespace-only input (e.g. `\" \"`). Despite being marked as required, the form still allows submission and creates the patient record, saving empty looking values for those fields.\n\nThis breaks the required field validation logic.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patient Section\n2. Click on Add New patient\n3. Fill the form \n4. See error\n\n**Expected behavior**\nIf a user enters only whitespace in any required field, it should be treated the same as leaving it empty:\n- A validation error should appear (e.g. “This field is required”)\n- The form should not be submitted until valid text is entered\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/eb0cbc78-093f-460a-9b46-a393e4533e7e\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],12948,"Whitespace Bypasses Required Validation in Patient Form Fields","2025-07-21T08:05:07Z","https://github.com/ohcnetwork/care_fe/issues/12948",0.7043986,{"description":3253,"labels":3254,"number":3257,"owner":3172,"repository":3173,"state":3183,"title":3258,"updated_at":3259,"url":3260,"score":3261},"**Describe the bug**\nOn the User Information page, when editing the password fields (Current Password, New Password, and Confirm New Password), I noticed that two eye icons appear inside the input field, one from our code and one injected by the browser (likely default). Both perform the same toggle, but it looks redundant and might confuse users.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Navigate to the User Information page.\n2. Go to the Reset Password section.\n3. Start typing into any of the password fields (Current Password, New Password, or Confirm New Password).\n4. Observe that two \"eye\" icons appear for toggling password visibility.\n\n**Expected behavior**\nOnly one visibility toggle icon should appear per password field, which toggles the visibility of that specific field.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/66d6b3b8-c118-4f01-ab35-4ede3b442a0a\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3255,3256],{"name":3200,"color":3201},{"name":3203,"color":3204},12877,"Duplicate Password Visibility Toggle Icons Appearing","2025-07-14T08:12:40Z","https://github.com/ohcnetwork/care_fe/issues/12877",0.7058684,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9XPehRBr-TJNaNUja9yABpddsIm6tND5xVDHqXjVjk8":-1},"/ohcnetwork/care_fe/12529"]