\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",[],13305,"Validation Errors Not Displayed as Expected for Schedule Edit Form ","2025-08-10T18:45:31Z","https://github.com/ohcnetwork/care_fe/issues/13305",0.8125125,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\nIn the Add Device form, under Add Contact Point, the validation error messages are not cleared when switching between different contact point types.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Add Device form.\n2. Add a contact point with type = Email.\n3. Enter an invalid email → validation message \"Invalid email\" appears (expected).\n4. Now switch the type to URL (or any other option).\n5. The previous \"Invalid email\" validation error still persists.\n\n**Current Behavior:**\n\n- Validation error message remains even after switching the contact point type.\n- Some Error also persists even after clearing the field.\n\n**Expected behavior**\n\n- Validation error should reset/clear when the user switches to a new contact point type.\n- Only the validation rules of the **currently selected type** should apply.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/f7fb3584-679d-4b41-9e53-e2ed417d83b9\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",[],13463,"Validation error persists after changing Contact Point type in Add Device form","2025-08-21T20:39:51Z","https://github.com/ohcnetwork/care_fe/issues/13463",0.81811625,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Describe the bug**\nThere are couple of bugs in the Product Knowledge form\n- currently `Name` field shows generic 'Required' instead of `Name is required` message\n- in the UI, `Base Unit` is marked as required field but when left empty, no required message shown in the UI.\n- even though `definitional` is optional, still while creating the form, `Dosage Form` shows required message. \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n\n**Expected behavior**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/10ec5758-79f1-439c-85b4-52f28a2e20e9\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",[],14023,"validation issues in Product Knowledge form","2025-10-09T18:15:22Z","https://github.com/ohcnetwork/care_fe/issues/14023",0.8239494,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3174,"title":3207,"updated_at":3208,"url":3209,"score":3210},"**Describe the bug**\nWhen we are searching using different options, it is showing no entries with the phone number for all options.\nAlso Aadhar number is only numeric but user is able to enter text content.\n\nhttps://github.com/user-attachments/assets/4a003557-890b-4885-81c3-acaa38a542e8\n\n\n**Expected behavior**\nWe can render a generalize text for different options\nAadhar number should be restricted to numeric just like the phone number.\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\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",[],13006,"Bug: Generalise the text when there is no entry for a search input in Patient earch","2025-07-21T05:07:46Z","https://github.com/ohcnetwork/care_fe/issues/13006",0.82859206,{"description":3212,"labels":3213,"number":3214,"owner":3172,"repository":3173,"state":3215,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**Description**: Currently, the form allows users to enter the same value for phone number and emergency phone number even when the \"same phone number\" checkbox is unchecked.\n\nThis creates inconsistent data, since the emergency contact should be different unless explicitly set via the checkbox.\n\n\u003Cimg width=\"508\" height=\"273\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cd341bf5-3d5a-4a1a-a540-85492d02ea9f\" />\n\n**Expected Behavior**\n- If same_phone_number is checked → no error (emergency phone is auto-filled from phone).\n- If same_phone_number is unchecked → an error must be raised if phone_number === emergency_phone_number.\n\n---\n🚨 DO NOT EDIT BELOW THIS LINE 🚨\nInstructions for Requesting Assignment:\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\nDescribe 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\nExpected Timeline:\n\nEnd date: [Expected submission date of a completed Pull Request]\nAdditional 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\n\n",[],13701,"closed","Validation: Emergency phone number should not match phone number if checkbox is unchecked","2025-09-17T10:51:48Z","https://github.com/ohcnetwork/care_fe/issues/13701",0.75653076,{"description":3221,"labels":3222,"number":3235,"owner":3172,"repository":3173,"state":3215,"title":3236,"updated_at":3237,"url":3238,"score":3239},"**Describe the bug**\nWhen registering a new patient, if we check the \"phone for emergency contact\" checkbox, the validation error message for the Emergency Phone Number field does not disappear.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Patients' -> \"Add new patient\".\n2. Check the \"Use this phone number for emergency contact\" checkbox.\n3. Observe that the validation message for Emergency Phone Number remains visible.\n\nhttps://github.com/user-attachments/assets/14859aad-dcc1-491c-b6a1-6d89afb74fa8\n\n**Expected behavior**\nThe validation error for Emergency Phone Number should disappear as the checkbox is checked.\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\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",[3223,3226,3229,3232],{"name":3224,"color":3225},"good first issue","7057ff",{"name":3227,"color":3228},"question","d876e3",{"name":3230,"color":3231},"stale","688388",{"name":3233,"color":3234},"needs-triage","ededed",13227,"Emergency Contact Field Error Not Dismissing on Checkbox Selection","2025-08-21T13:56:21Z","https://github.com/ohcnetwork/care_fe/issues/13227",0.77647686,{"description":3241,"labels":3242,"number":3243,"owner":3172,"repository":3173,"state":3215,"title":3244,"updated_at":3245,"url":3246,"score":3247},"**Describe the bug**\nWhen selecting the checkbox for an emergency number, validation error is displayed.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Patient Registration.'\n2. Click on check box of same as emergency number.\n3. . See error , validation error is showing.\n\nhttps://github.com/user-attachments/assets/c247ff3d-10a8-4443-add5-f9b3df2b5d65\n\n**Expected behavior**\nNo validation error should be triggered when the checkbox is selected\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\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",[],13490,"Incorrect Error Message on Emergency Contact Field","2025-08-25T14:40:26Z","https://github.com/ohcnetwork/care_fe/issues/13490",0.78223115,{"description":3249,"labels":3250,"number":3253,"owner":3172,"repository":3173,"state":3215,"title":3254,"updated_at":3255,"url":3256,"score":3257},"**Describe the bug**\nThe **Date of Birth** input component currently allows users to enter unrestricted character lengths (e.g., more than 2 digits for day or month, and more than 4 digits for year). \n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Facility' > 'Patient' > 'Search patient'\n2. Click on 'Add New Patient'\n3. Scroll down to 'Date of Birth'\n4. Type as much as digits you want in that DD MM YY fields.\n\n**Expected behavior**\n\n- The \"Day\" input should restrict input to 2 digits only.\n- The \"Month\" input should also restrict to 2 digits.\n- The \"Year\" input should be limited to 4 digits, ideally up to the current year.\n- After entering 2 digits in Day and Month fields, the cursor should automatically move to the next input field to improve UX.\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/6eb06855-70dd-447c-a7f5-fa4c0e10aac8\n\n**Desktop (please complete the following information):**\n\n- OS: Windows 11\n- Browser chrome\n- Version 115+\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**\nAdditionally will have to add auto-focus behavior between fields so that the cursor automatically move to \"MM\", and then to \"YYYY\", otherwise it will affects user experience.\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",[3251,3252],{"name":3227,"color":3228},{"name":3233,"color":3234},13289,"Bug: Date of Birth (DOB) Inputs Allow Unlimited Characters - In Create New Patient Form","2025-08-08T04:12:59Z","https://github.com/ohcnetwork/care_fe/issues/13289",0.7921481,{"description":3259,"labels":3260,"number":3263,"owner":3172,"repository":3173,"state":3215,"title":3264,"updated_at":3265,"url":3266,"score":3267},"Please enhance the questionnaire settings to allow users to enter longer responses in fields with the 'text' data type.\nAs it now limited to 500 words only which needs to be increased more as nurse need more characters to type in investigation, history .for case summary preparation.\n2000 characters would solved this issue.\n",[3261,3262],{"name":3227,"color":3228},{"name":3233,"color":3234},12760,"Increase the character limit for text-type responses in the questionnaire","2025-07-10T07:47:55Z","https://github.com/ohcnetwork/care_fe/issues/12760",0.80484957,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQPumn-Bu5PLt7X1xNn6dvazxCgK51PgLNfDmmJfx9C8":-1},"/ohcnetwork/care_fe/13613"]