\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",[],13303,"ohcnetwork","care_fe","open","Checkbox logic & UI misalignment issues in \"Add Patient Details\" form","2025-08-07T14:43:13Z","https://github.com/ohcnetwork/care_fe/issues/13303",0.6835271,{"description":3091,"labels":3092,"number":3093,"owner":3083,"repository":3084,"state":3085,"title":3094,"updated_at":3095,"url":3096,"score":3097},"**Describe the bug**\nWhen we are removing a field and trying to add it back in patient information section, we are not able to add it.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/facility/2fbb0809-b62c-4c53-816e-f1404f096c5e/settings/reportbuilder/new)\n2. Click on Section Tab\n3. Remove a field and try to add it back\n4. See error\n\n**Expected behavior**\nUser should able to add field\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/26eece7a-a1aa-4425-9c19-06bd23612861\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",[],12477,"Bug: User is not able to add field in Patient Information section of Report Template Builder","2025-06-01T11:01:17Z","https://github.com/ohcnetwork/care_fe/issues/12477",0.69537777,{"description":3099,"labels":3100,"number":3101,"owner":3083,"repository":3084,"state":3102,"title":3103,"updated_at":3104,"url":3105,"score":3106},"**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,"closed","Whitespace Bypasses Required Validation in Patient Form Fields","2025-07-21T08:05:07Z","https://github.com/ohcnetwork/care_fe/issues/12948",0.53791046,{"description":3108,"labels":3109,"number":3113,"owner":3083,"repository":3084,"state":3102,"title":3114,"updated_at":3115,"url":3116,"score":3117},"**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",[3110],{"name":3111,"color":3112},"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.6409443,{"description":3119,"labels":3120,"number":3121,"owner":3083,"repository":3084,"state":3102,"title":3122,"updated_at":3123,"url":3124,"score":3125},"**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.64872086,{"description":3127,"labels":3128,"number":3129,"owner":3083,"repository":3084,"state":3102,"title":3130,"updated_at":3131,"url":3132,"score":3133},"**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.65390235,{"description":3135,"labels":3136,"number":3144,"owner":3083,"repository":3084,"state":3102,"title":3145,"updated_at":3146,"url":3147,"score":3148},"**Describe the bug**\nWhen attempting to log in, if the user enters only spaces before/after username and password fields, the form is accepted and a login request is sent. \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Login ' page\n2. Enter spaces (e.g., \" administrator_2_0 \") in the Username field.\n3. Enter spaces (e.g., \" Coronasafe@123 \") in the Password field.\n4. Click Login.\n5. Observe that the form is submitted & dashboard opened, instead of showing a validation error.\n\n**Expected behavior**\nInputs containing only whitespace should be treated as empty, and form submission should be blocked with an appropriate validation message, such as:\n**- Please enter a valid username/password”**\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/55e3f6c9-24f9-4b6f-951f-c4061eaa608e\n\n**Desktop (please complete the following information):**\n\n- OS: [Windows 11]\n- Browser [Chrome]\n- Version [138.0.7204.184 (Official Build) (64-bit)]\n\n**Additional context**\n- Neither username nor password fields are trimmed on input before validation.\n- Trimming should be applied before checking for emptiness or format.\n- This issue can lead to unnecessary backend load and a poor user experience.\n\n**✅ QA Suggestion:**\nCurrently, there is **no Cypress test** that checks login behavior with leading/trailing spaces in credentials.\n\n**Suggested Test Case Name:** \n`should NOT allow login with leading/trailing spaces in username or password`\n\n**Description:** \nSimulates a login attempt where the username and/or password fields have unintended whitespace at the beginning or end. The test should assert that:\n- Login fails (user is **not redirected to /dashboard**)\n- An appropriate error message is shown (e.g., “Invalid credentials”)\n\n**Location to add the test:** \n`care_fe/cypress/e2e/login_spec/loginpage.cy.ts`\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",[3137,3140,3141],{"name":3138,"color":3139},"question","d876e3",{"name":3111,"color":3112},{"name":3142,"color":3143},"needs-triage","ededed",13226,"[Bug] [QA] : Login accepts leading/trailing whitespace in username and password","2025-08-21T14:44:11Z","https://github.com/ohcnetwork/care_fe/issues/13226",0.66169226,{"description":3150,"labels":3151,"number":3152,"owner":3083,"repository":3084,"state":3102,"title":3153,"updated_at":3154,"url":3155,"score":3156},"**Describe the bug**\nIn the **Patient Details** > **Files** tab, when recording audio and uploading it, the \"Enter File name\" field allows users to enter only whitespaces (e.g., \" \"). Upon saving, the file is uploaded with **.mp3** as the name, which looks empty and confusing.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patient Details → Files tab.\n2. Click on Add Files then Record Audio and finish a recording.\n3. In the Enter File Name field, input only spaces.\n4. Click Upload and observe that the file is saved as `.mp3`.\n\n**Expected behavior**\n- The file name field should validate the input.\n- Whitespaces-only should be treated as an empty value.\n- Show an error/toast if no valid file name is provided.\n- Prevent the upload until a valid file name is entered.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/02caa4b8-d6d7-4fe4-8efe-ce014416f368\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",[],13100,"File upload for audio recording allows whitespace-only file name","2025-07-28T04:56:55Z","https://github.com/ohcnetwork/care_fe/issues/13100",0.66866827,{"description":3158,"labels":3159,"number":3162,"owner":3083,"repository":3084,"state":3102,"title":3163,"updated_at":3164,"url":3165,"score":3166},"**Describe the bug**\nIn mobile view, the config card shows incorrect line breaks and awkward spacing not only for the name, but also for the status badge (\"Inactive\") and the description text. This leads to poor readability and inconsistent UI.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Admin Dashboard\n2. Click on Patient Identifier Config\n3. Scroll down to Card with detials\n4. See error\n\n**Expected behavior**\nThe config card should display the name, status badge, and description in a clear, continuous layout with proper wrapping and spacing, maintaining consistency regardless of screen size.\n\n**Screenshots**\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**\nThe ValueSet preview has consistent UI even for small screens, replicaitng it here could solve this issue\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",[3160,3161],{"name":3138,"color":3139},{"name":3142,"color":3143},13500,"Patient Identifier Config Card Name Breaks Incorrectly in Mobile View","2025-08-25T14:46:52Z","https://github.com/ohcnetwork/care_fe/issues/13500",0.6719607,{"description":3168,"labels":3169,"number":3170,"owner":3083,"repository":3084,"state":3102,"title":3171,"updated_at":3172,"url":3173,"score":3174},"**Describe the bug**\n\nWhen we upload files from the device and enter just whitespaces on the file name. The system validates it can the file is added. \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Encounter Files\n2. Click on Add Files\n3. Click on Upload From Device and select a file\n4. Enter white spaces for the file name and upload\n5. See error\n\n**Expected behavior**\n\nIf the file name is just white spaces the system should not pass it through\n\n**Recording**\n\nhttps://github.com/user-attachments/assets/bf5b8b41-796d-4161-9d1a-dcc7ab1aa507\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",[],13088,"Bug: Entering white space for file name passes the validation","2025-07-31T11:51:47Z","https://github.com/ohcnetwork/care_fe/issues/13088",0.6738776,["Reactive",3176],{},["Set"],["ShallowReactive",3179],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRNAwHaIHD0UjCLtH86qH4tcfDVjOMGbqiwRuO_kzM88":-1},"/ohcnetwork/care_fe/13312"]