\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",[],13629,"ohcnetwork","care_fe","open","Gender field can be deselected, shows wrong error","2025-09-05T14:19:22Z","https://github.com/ohcnetwork/care_fe/issues/13629",0.7214432,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Describe the bug**\nOn the **Appointments** page, the Search Patients feature has two options:\n1. Search by Patient Name\n2. Search by Phone Number\n\nCurrently:\n- In Search by Phone Number, users can enter strings (letters/characters).\n- In Search by Patient Name, users can enter numbers (like phone numbers).\n\nThis causes confusion and allows invalid searches.\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Appointments → Search Patients.\n2. Select Search by Phone Number.\n3. Enter a string (e.g., \"abcd\").\n4. Observe that the input is accepted.\n5. Switch to Search by Patient Name and enter a number (e.g., \"9876543210\").\n6. Observe that the input is also accepted.\n\n**Expected behavior**\n- Search by Phone Number: Should restrict input to **digits** only.\n- Search by Patient Name: Should restrict input to **letters** only.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/bc154bf6-8c6b-45b1-8bcc-fe0cf38be727\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",[],13953,"Patient Search Input Allows Invalid Data Types","2025-10-03T16:20:16Z","https://github.com/ohcnetwork/care_fe/issues/13953",0.72876596,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3191,"title":3192,"updated_at":3193,"url":3194,"score":3195},"**Describe the bug**\nWhen I was inputting a character \"e\" in the decimal and integer type of a question, I observed an incorrect error message as \" This field is required\" instead of showing an error message as \"Invalid input type\" .\n\nSTEPS TO REPRODUCE :\n\n\u003Cimg width=\"1738\" height=\"922\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ee295229-6d82-47d4-9e02-2755c811ab1c\" />\n\n1) Create a questionnaire with decimal / integer type \n2) Access the questionnaire from encounter section of patient.\n3) Try inputting the field of decimal and integer type with \"e\".\n4) It will show an error message as \" This field is required\" instead of \" Invalid input type \"\n\nEXPECTED BEHAVIOR\nThe system should return an error message like:\n“Please enter a valid number” or “Input must be an integer/decimal”\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",[],12970,"closed","Incorrect error message when wrong input type is entered in questionnaire (e.g., string in decimal/integer field)","2025-08-22T11:07:57Z","https://github.com/ohcnetwork/care_fe/issues/12970",0.6906871,{"description":3197,"labels":3198,"number":3199,"owner":3172,"repository":3173,"state":3191,"title":3200,"updated_at":3201,"url":3202,"score":3203},"**Describe the bug**\nWhen using number input fields (`type=\"number\"`), users can enter the scientific notation character 'e' (or 'E'), which is not desired behavior for fields like dates, pincodes, and age inputs.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any form\n2. Click on number only input\n3. Type 'e'\n4. See error\n\n**Expected behavior**\n- Number input fields should only accept digits (0-9)\n- Scientific notation characters ('e', 'E') should be prevented\n- This is especially important for fields like dates, pincodes, and age where scientific notation is not meaningful\n\n**Screenshots**\n\n\n\n**Desktop (please complete the following information):**\n\n- OS: Fedora\n- Browser: Brave\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",[],12545,"Bug: Scientific notation 'e' character can be entered in number input fields","2025-06-09T10:16:08Z","https://github.com/ohcnetwork/care_fe/issues/12545",0.7186115,{"description":3205,"labels":3206,"number":3210,"owner":3172,"repository":3173,"state":3191,"title":3211,"updated_at":3212,"url":3213,"score":3214},"**Describe the bug**\nThe keyword field on the public patient registration page currently uses the normal keyboard on mobile devices, making it less user-friendly for numeric input. This causes friction for users expected to enter numbers for age\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Login as Patient with otp : 45612\n2. Click on `Book Appointment`\n3. Book a slot where you would see Add Patient button which opens up Registration page \n4. See error\n\n**Expected behavior**\nIt should have numpad (like numpad shown in video for date field) instead of normal keyword to prevent unwanted problems\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/f030b51f-1827-444e-a4d9-36f0d230a4b9\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",[3207],{"name":3208,"color":3209},"good first issue","7057ff",12682,"Update the input mode to numpad for Age Input in Public Patient Registration Form","2025-06-25T10:24:47Z","https://github.com/ohcnetwork/care_fe/issues/12682",0.7247317,{"description":3216,"labels":3217,"number":3218,"owner":3172,"repository":3173,"state":3191,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**Describe the bug**\nBroken UI in encounter view after adding vitals in doctors form.\n\n**To Reproduce**\n\n\n1. Go to View encounter\n2. Click on add questionnaire and add doctors form. Fill vitals\n3. See error\n\n\n**Screenshots**\n\n\u003Cimg width=\"1452\" height=\"899\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/4171c175-14b4-4d19-9dac-df72c82f5e16\" />\n\n**Desktop (please complete the following information):**\n\n- iOS\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",[],13438,"Broken UI in encounter view after adding vitals","2025-09-01T11:17:48Z","https://github.com/ohcnetwork/care_fe/issues/13438",0.7256897,{"description":3224,"labels":3225,"number":3226,"owner":3172,"repository":3173,"state":3191,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**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.7272382,{"description":3232,"labels":3233,"number":3234,"owner":3172,"repository":3173,"state":3191,"title":3235,"updated_at":3236,"url":3237,"score":3238},"**Is your feature request related to a problem? Please describe.**\nYes, as of now in the `Patient Identifier Config` and `Tag config`, while **creating** a new or **editing** the Patient Identifier Config Form and Tag config Form, even if there are no changes are made while editing or no values are entered or selected while creating the respective **Button** stays enables. This creates a false sense of action and could lead to confusion or unnecessary backend operations.\n\n**Describe the solution you'd like**\nWe should disable the button while creating and updating until any required changes are made\n\n**Describe alternatives you've considered**\nA clear and concise description of any alternative solutions or features you've considered.\n\n**Additional context**\n\nhttps://github.com/user-attachments/assets/6e51e145-34f5-4120-b8d0-bd55fc5fc950\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",[],13115,"Disable Submit Button Until Valid Changes Are Made in Config Forms","2025-08-19T06:58:17Z","https://github.com/ohcnetwork/care_fe/issues/13115",0.72761786,{"description":3240,"labels":3241,"number":3242,"owner":3172,"repository":3173,"state":3191,"title":3243,"updated_at":3244,"url":3245,"score":3246},"**Describe the bug**\nUI is congested when we are enabling conditions in patient death form questionnaire. The three fields i.e. Question, Operator and Answer are degrading the user experience.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/admin/questionnaire/death-form12/edit)\n2. Go to Death Time Question and Click on 'Enable when conditions'\n3. See in mobile view\n4. See error\n\n**Expected behavior**\nAll three fields should be in separate line so that user can see what he is typing. \n\n**Screenshots**\n\n\u003Cimg width=\"254\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/4212fb65-a7cf-4b70-b20b-f779634e6a64\" />\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",[],12530,"Bug: Misalignment in fields of Death Time form of Patient Death Form Questionnaire","2025-06-09T02:34:27Z","https://github.com/ohcnetwork/care_fe/issues/12530",0.7297366,{"description":3248,"labels":3249,"number":3253,"owner":3172,"repository":3173,"state":3191,"title":3254,"updated_at":3255,"url":3256,"score":3257},"**Describe the bug**\nIn the **\"Add Patient Details\"** form, there are two issues:\n1. **Confusing Validation with Address Checkbox**\nWhen the checkbox **\"Use this address for permanent address\"** is selected, and the **Current Address** field is left empty, the form throws a “Required” validation error for **both Current and Permanent Address fields**.\nThis is confusing because the user has opted to use the current address as permanent, yet the validation message make it seem like they are still required to fill both fields manually.\n\n2. **Misaligned \"Required\" Label**\nThe **\"Required\"** label for the **State** field appears visually misaligned compared to other fields in the form.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to \"Add Details of Patient\" form.\n2. Leave the Current Address field empty.\n3. Check the box **\"Use this address for permanent address\"**.\n4. See error\n\n**Expected behavior**\n- If the checkbox is selected, only the Current Address field should show that validation message\n- The **\"Required\"** label for the State field should be properly aligned with the others.\n\n**Screenshots**\n\n\u003Cimg width=\"1012\" height=\"421\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/53514cf7-5581-4143-bd13-1c5cd83b139e\" />\n\n\u003Cimg width=\"917\" height=\"367\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8207c67e-4615-41dd-81c2-0f7798413842\" />\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",[3250],{"name":3251,"color":3252},"stale","688388",13303,"Checkbox logic & UI misalignment issues in \"Add Patient Details\" form","2025-10-01T10:37:54Z","https://github.com/ohcnetwork/care_fe/issues/13303",0.73049504,["Reactive",3259],{},["Set"],["ShallowReactive",3262],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fXOHz1_5XRCdZ7MtLv1v2BAQx-tfL0gYdd-Y9_1dyafQ":-1},"/ohcnetwork/care_fe/12775"]