\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",[],13641,"Text not properly aligned in profile page","2025-09-07T07:38:31Z","https://github.com/ohcnetwork/care_fe/issues/13641",0.7829413,{"description":3204,"labels":3205,"number":3215,"owner":3172,"repository":3173,"state":3216,"title":3217,"updated_at":3218,"url":3219,"score":3220},"**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",[3206,3209,3212],{"name":3207,"color":3208},"question","d876e3",{"name":3210,"color":3211},"stale","688388",{"name":3213,"color":3214},"needs-triage","ededed",13226,"closed","[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.6103094,{"description":3222,"labels":3223,"number":3224,"owner":3172,"repository":3173,"state":3216,"title":3225,"updated_at":3226,"url":3227,"score":3228},"**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.70286554,{"description":3230,"labels":3231,"number":3232,"owner":3172,"repository":3173,"state":3216,"title":3233,"updated_at":3234,"url":3235,"score":3236},"**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.7285252,{"description":3238,"labels":3239,"number":3240,"owner":3172,"repository":3173,"state":3216,"title":3241,"updated_at":3242,"url":3243,"score":3244},"**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.73072666,{"description":3246,"labels":3247,"number":3248,"owner":3172,"repository":3173,"state":3216,"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.73237973,{"description":3254,"labels":3255,"number":3258,"owner":3172,"repository":3173,"state":3216,"title":3259,"updated_at":3260,"url":3261,"score":3262},"**Describe the bug**\nWhen we are submitting user form without password, the focus is shifting to the confirm password field. Also the validations in password fields are optional in frontend.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](http://localhost:4000/organization/0b769676-a71b-49fc-8187-b8d81101109e/users?page=1&limit=15)\n2. Click on Add new user\n3. Fill all the details except password and submit\n4. See error\n\n**Expected behavior**\n\nhttps://github.com/user-attachments/assets/6c0bb605-2b69-4304-8654-f8e47cddab97\n\n**Current Behavior**\n\nhttps://github.com/user-attachments/assets/a7a5ab7d-106b-41de-b9b0-993536a9b811\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",[3256,3257],{"name":3207,"color":3208},{"name":3213,"color":3214},12529,"Bug: Validations required in User Form for password fields to shift the focus in right field","2025-07-31T05:12:35Z","https://github.com/ohcnetwork/care_fe/issues/12529",0.7417389,["Reactive",3264],{},["Set"],["ShallowReactive",3267],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqrYSnO9uL1QDw25hxPq9RHdUmAl47NKUubfZ2zTOP_8":-1},"/ohcnetwork/care_fe/13228"]