\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",[],13274,"Fix the spacing in the patient notes post submission ( Patient encounter & details page )","2025-08-06T07:02:56Z","https://github.com/ohcnetwork/care_fe/issues/13274",0.7560091,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3199,"title":3200,"updated_at":3201,"url":3202,"score":3203},"**Describe the bug**\nWhen cancelling an appointment, if the user enters only spaces in the \"Note\" field, It accepts it and submits the cancellation. \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Encounters' -> \"View Patients\" -> \"Appointments\"\n2. Click on ''Cancel Appointment\"\n3. See error, it accepts a note with spaces.\n\nhttps://github.com/user-attachments/assets/3a5b849a-58ff-4770-b6fe-53e96f7865f5\n\n**Expected behavior**\nThe reason should never appear as empty after cancelling an appointment.\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",[],13025,"closed","Note Field Accepts Spaces as Valid Input","2025-08-04T07:12:19Z","https://github.com/ohcnetwork/care_fe/issues/13025",0.6712345,{"description":3205,"labels":3206,"number":3210,"owner":3172,"repository":3173,"state":3199,"title":3211,"updated_at":3212,"url":3213,"score":3214},"**Describe the bug**\nWhen submitting whitespace-only input (space) in these fields: \n- **Encounter Page** → Notes section \n- **Resource Requests** → Reason for Request field \n\nThe system accepts it as valid input, creating: \n- Empty notes that clutter the UI \n- Resource requests with blank reasons\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to encouter page or resource request page\n2. Click on Add Allergy, Add Diagnosis, and Add Symptom or reason of request section\n3. Just enter a space and submit\n4. See error\n\n**Expected behavior**\nUser should not be able to create empty notes, Also reason of request is not supposed to by bypassed with a whitespace.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/f992b635-b1de-400c-9363-9c483b2f2623\n\n\n\n\n\n\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},"stale","688388",12621,"Entering just whitespace in input fields still creates empty entries","2025-07-29T20:22:14Z","https://github.com/ohcnetwork/care_fe/issues/12621",0.70973206,{"description":3216,"labels":3217,"number":3218,"owner":3172,"repository":3173,"state":3199,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**Describe the bug**\nIn the Doctor Schedule Template creation form, the optional `Remarks` field accepts whitespace-only input (e.g. spaces). This gets saved as a valid remark even though no actual content was provided. that may violate UX expectations and unnecessary DB storage\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Log in as a doctor\n2. In the overview page click on My Schedules and then create one Template.\n3. while filling the Remarks field, add only whitespaces\n4. See error\n\n**Expected behavior**\nIf the user enters only whitespace in the `Remarks` field, it should be treated as empty (`null` or `\"\"`) and not be saved or submitted as a valid remark.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/0ae1be48-effc-4065-b393-5b4663f2982e\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",[],12888,"Whitespace-only input in optional \"Remarks\" field is treated as valid text in Create Schedule Template.","2025-07-18T07:01:47Z","https://github.com/ohcnetwork/care_fe/issues/12888",0.70995766,{"description":3224,"labels":3225,"number":3232,"owner":3172,"repository":3173,"state":3199,"title":3233,"updated_at":3234,"url":3235,"score":3236},"**Description:** When creating or editing queues, the system accepts whitespace characters (spaces, tabs, etc.) as valid names. and The same behaviour is found while creating a service point too.\n\nhttps://github.com/user-attachments/assets/8f39ca59-265f-480f-bc4a-06a1956ef275\n\n**Steps to Reproduce:**\n\nQueues\n- Navigate to queue creation\n- Enter only spaces/tabs in the name field\n- Save the queue\n- Observe that the system accepts the invalid input, and same while editing the queue\n\nServicePoints\n- Navigate to service point\n- Enter only spaces/tabs in the name field\n- Save the service point\n\n",[3226,3229],{"name":3227,"color":3228},"question","d876e3",{"name":3230,"color":3231},"needs-triage","ededed",13825,"Queue creation and editing allows whitespace (\" \")","2025-10-06T12:19:38Z","https://github.com/ohcnetwork/care_fe/issues/13825",0.717291,{"description":3238,"labels":3239,"number":3240,"owner":3172,"repository":3173,"state":3199,"title":3241,"updated_at":3242,"url":3243,"score":3244},"**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.7191222,{"description":3246,"labels":3247,"number":3248,"owner":3172,"repository":3173,"state":3199,"title":3249,"updated_at":3250,"url":3251,"score":3252},"**Describe the bug**\nIn both the Tag Config and Roles (RBAC) sections, the description field accepts input that contains only whitespace characters. \nThis leads to:\n\n- **Empty-looking description fields being saved and displayed**.\n\n\u003Cimg width=\"1500\" height=\"460\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/32ecbe57-7398-48eb-a002-77e2e87fdc2b\" />\n\n\n- **Inconsistent UI sometimes the description field is blank, and other times it shows a dash (-) when left empty.**\n\n\u003Cimg width=\"1526\" height=\"803\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/84231500-677c-4765-ac2b-cf6efc13e8e2\" />\n\n**To Reproduce**\nSteps to reproduce For Tag Config:\n\n1. Go to Tag Config → Click Add Tag.\n2. In the Description field, input only spaces\n3. Click Create Tag.\n4. Tag gets created and on viewing it, the description appears blank instead of not appearing\n\nSteps to reproduce for Roles:\n1. Go to Roles (RBAC) → Click Add Role.\n2. In the Description field, input only spaces.\n3. Click Create Role\n4. The role gets created and on viewing it, the description shows an empty space instead of the fallback dash (`-`).\n\n**Expected behavior**\nWhen whitespace is entered, it should be treated as empty space\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",[],13085,"Description Field Accepts Whitespaces in Roles and Tag Config Page","2025-07-25T13:29:05Z","https://github.com/ohcnetwork/care_fe/issues/13085",0.72264826,{"description":3254,"labels":3255,"number":3256,"owner":3172,"repository":3173,"state":3199,"title":3257,"updated_at":3258,"url":3259,"score":3260},"**Describe the bug**\nIn the newly created appointments view, the badge text spacing is not even. There is more space in the top compare to the bottom.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Appointments'\n2. See error\n\n**Expected behavior**\nThe y-space should be equal.\n\n**Screenshots**\n\n\u003Cimg width=\"1338\" height=\"406\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/41525077-93c0-48dc-a531-26fd89b29bf1\" />\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",[],13051,"Uneven Vertical Padding in Badge Text on Appointments View","2025-08-13T18:01:02Z","https://github.com/ohcnetwork/care_fe/issues/13051",0.7269902,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fi1CYzdxL2GB2h63cnE8SnLHPIx7k3Ie_uaYBEkWTXow":-1},"/ohcnetwork/care_fe/12673"]