\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",[],12889,"Add * mark on required fields and disable save button initially in Discount Code Sheet","2025-07-13T04:55:10Z","https://github.com/ohcnetwork/care_fe/issues/12889",0.7067527,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"**Description:** Edit Schedule Template Form is accepting white space.\n\nhttps://github.com/user-attachments/assets/78db4434-cdf5-4913-9709-732011f287ca\n\n**Steps to Reproduce:**\n- Navigate to Edit Schedule Template Form.\n- Enter a blank space (\" \") in the Template name Field.\n- Submit the form.\n- Observe that the form accepts the input instead of showing validation error.\n\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\n",[],13775,"closed","Edit Schedule Template accept blank inputs (\" \")","2025-09-22T08:40:37Z","https://github.com/ohcnetwork/care_fe/issues/13775",0.6726741,{"description":3213,"labels":3214,"number":3215,"owner":3172,"repository":3173,"state":3207,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**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.67539,{"description":3221,"labels":3222,"number":3223,"owner":3172,"repository":3173,"state":3207,"title":3224,"updated_at":3225,"url":3226,"score":3227},"**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.67937547,{"description":3229,"labels":3230,"number":3231,"owner":3172,"repository":3173,"state":3207,"title":3232,"updated_at":3233,"url":3234,"score":3235},"**Describe the bug**\nSave button allows submitting form without making any changes.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings\" -> \"Billing\" -> \"Edit button\"\n2. See error, without changing any fields, click Save.Form submits.\n\nhttps://github.com/user-attachments/assets/00805337-2f05-4af5-b145-65ec89e06281\n\n**Expected behavior**\nSave should be disabled until the form is modified\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",[],13452,"Discount Code form allows saving without changes","2025-08-21T14:16:19Z","https://github.com/ohcnetwork/care_fe/issues/13452",0.6855211,{"description":3237,"labels":3238,"number":3242,"owner":3172,"repository":3173,"state":3207,"title":3243,"updated_at":3244,"url":3245,"score":3246},"**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",[3239],{"name":3240,"color":3241},"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.68794775,{"description":3248,"labels":3249,"number":3257,"owner":3172,"repository":3173,"state":3207,"title":3258,"updated_at":3259,"url":3260,"score":3261},"**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",[3250,3253,3254],{"name":3251,"color":3252},"question","d876e3",{"name":3240,"color":3241},{"name":3255,"color":3256},"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.696534,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$foDooIA1rPwN9FvwNdhijf2kbPBfLY6HVbcrqc36k5sg":-1},"/ohcnetwork/care_fe/14021"]