\n\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",[],13989,"Validation is malfunctioning in the healthcare service edit page","2025-10-07T13:03:03Z","https://github.com/ohcnetwork/care_fe/issues/13989",0.726143,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**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.7349888,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Describe the bug**\nWhen toggling the Auto-fill slot duration switch in the schedule template form, the Number of slots input throws a React warning:\n\"Input contains an input of type number with both value and defaultValue props.\nInput elements must be either controlled or uncontrolled (specify either the value prop, or the defaultValue prop, but not both).\"\n\nThis happens because the Input component is being passed both value (from react-hook-form) and defaultValue simultaneously.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to overview → Users → Create Schedule Template.\n2. Scroll to the Auto-fill slot duration toggle and enable it.\n3. The Number of slots input becomes visible.\n4. Observe the console warning in DevTools.\n\n**Expected behavior**\nThe input field should work without throwing controlled/uncontrolled warnings. It should only use value (via react-hook-form) or defaultValue (but not both).\n\n**Screenshots**\n\n\u003Cimg width=\"1917\" height=\"994\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/961f8b18-057f-4586-b67a-6769967b5ef2\" />\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**\nThe issue is caused in FormField → Input usage:\n\n\u003CInput\n type=\"number\"\n min={1}\n defaultValue={1} // ❌ conflict\n {...field} // includes value + onChange\n/>\n\nThis passes both value and defaultValue, leading to the React error.\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",[],13574,"Bug: Input field throws controlled/uncontrolled warning when using auto-fill slot duration toggle","2025-08-31T10:24:24Z","https://github.com/ohcnetwork/care_fe/issues/13574",0.7402977,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"**Describe the bug**\nIn the **Create Schedule Template form**, when the form is submitted with empty values, most fields correctly show user-friendly validation errors such as `\"This field is required\"`.\nHowever, the fields `Slot Duration` and `Patients per Slot` display raw validation errors:\n- `\"Expected number, received null\"` when left empty.\n- `\"Expected number, received nan\"` when input is typed and then cleared.\n\nThis results in a confusing and inconsistent user experience, especially for non-technical users\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Create Schedule Template page.\n2. Leave all fields empty and click **Save**.\n3. Observe the validation messages for all required fields.\n4. See error\n\n**Expected behavior**\nAll fields should show consistent and user-friendly validation messages:\n- If empty: `This field is required`\n- If invalid: `Please enter a valid number`\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/44622cee-2151-480f-aba6-2c2216c2b81e\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",[],13304,"closed","Inconsistent and Technical Validation Errors in “Create Schedule Template” Form","2025-08-11T17:34:26Z","https://github.com/ohcnetwork/care_fe/issues/13304",0.6031946,{"description":3213,"labels":3214,"number":3221,"owner":3172,"repository":3173,"state":3207,"title":3222,"updated_at":3223,"url":3224,"score":3225},"In the **Register New Patient** form, required fields do not show any validation message when left empty and submitted. This applies to **all required fields** in the form. \n\n## Steps to Reproduce \n1. Go to **Register New Patient** form. \n2. Leave one or more **required fields** (e.g., Name, Phone Number, etc.) empty. \n3. Click **Save/Submit**. \n4. Observe → no validation error messages appear. \n\nhttps://github.com/user-attachments/assets/dadbefa7-aedf-431a-bb87-1694af67a727\n\n## Expected Behavior \n- Required fields should trigger proper validation messages (e.g., *\"This field is required\"*) when left empty. \n- The form should not be submitted until required fields are filled.\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",[3215,3218],{"name":3216,"color":3217},"question","d876e3",{"name":3219,"color":3220},"needs-triage","ededed",13957,"Missing Required Field Validation in Register New Patient Form","2025-10-04T14:31:18Z","https://github.com/ohcnetwork/care_fe/issues/13957",0.702363,{"description":3227,"labels":3228,"number":3231,"owner":3172,"repository":3173,"state":3207,"title":3232,"updated_at":3233,"url":3234,"score":3235},"**Describe the bug**\n\nWhen we submit the form, and there is a error in the schedule create form / edit form, it is not auto scrolling to the error message, so users need to manually check for error\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to profile and create a schedule with past date\n2. submit the form\n3. See error\n\n**Expected behavior**\n\nAuto-scroll to the error message in the schedule create / edit form\n\n**Screenshots**\n\n\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",[3229,3230],{"name":3216,"color":3217},{"name":3219,"color":3220},12149,"Add auto-scroll to error fields in schedule creation / edit form","2025-07-22T07:37:10Z","https://github.com/ohcnetwork/care_fe/issues/12149",0.7132961,{"description":3237,"labels":3238,"number":3239,"owner":3172,"repository":3173,"state":3207,"title":3240,"updated_at":3241,"url":3242,"score":3243},"**Describe the bug**\nWhen an exception is added, the slot info text includes unexpected characters, making it unclear.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'My Schedules' \n2. Click on a date with an exception added\n3. See error\n\n**Expected behavior**\nThe message should clearly show intended and actual slots.\n\n**Screenshots**\n\n\u003Cimg width=\"1909\" height=\"888\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/270f210f-3d26-48e5-bcfb-15d0d1878af3\" />\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",[],13092,"Incorrect text shown for `session_slots_info_striked`","2025-07-30T11:30:15Z","https://github.com/ohcnetwork/care_fe/issues/13092",0.71771514,{"description":3245,"labels":3246,"number":3247,"owner":3172,"repository":3173,"state":3207,"title":3248,"updated_at":3249,"url":3250,"score":3251},"**Describe the bug**\nIn the **Patient Identifier Config** form and **Tag Config** Form, required fields like `Display`, `Description`, `System` and `Slug` accept only whitespace as valid input. This results in entries that appear blank but still pass validation.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Log in as Super admin\n2. Go to Patient Identifier Config Form or Tag Config Form\n3. Add whitespaces to required field\n4. See error\n\n**Expected behavior**\nWhitespace-only input should be treated as empty. These fields should trigger a **\"Required\"** validation error if the input contains only spaces.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/6df1a10f-c285-44a0-b62a-2a3d23340b8f\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",[],13312,"Whitespace Bypasses Validation in Required Fields in Config Forms","2025-08-22T11:20:01Z","https://github.com/ohcnetwork/care_fe/issues/13312",0.7281171,{"description":3253,"labels":3254,"number":3255,"owner":3172,"repository":3173,"state":3207,"title":3256,"updated_at":3257,"url":3258,"score":3259},"**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.730586,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgKV7tp14yYQP3hgGUWtVRwKyPYc2IFjh1OW5bEZkIyY":-1},"/ohcnetwork/care_fe/13305"]