\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,"ohcnetwork","care_fe","open","Uneven Vertical Padding in Badge Text on Appointments View","2025-07-23T07:07:49Z","https://github.com/ohcnetwork/care_fe/issues/13051",0.75671136,{"description":3037,"labels":3038,"number":3039,"owner":3029,"repository":3030,"state":3031,"title":3040,"updated_at":3041,"url":3042,"score":3043},"**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,"Incorrect error message when wrong input type is entered in questionnaire (e.g., string in decimal/integer field)","2025-07-17T12:25:43Z","https://github.com/ohcnetwork/care_fe/issues/12970",0.7777321,{"description":3045,"labels":3046,"number":3047,"owner":3029,"repository":3030,"state":3031,"title":3048,"updated_at":3049,"url":3050,"score":3051},"**Describe the bug**\nCurrently, there is card view for medium screen which doesn't look good and makes like a lot of empty space \n\n**To Reproduce**\n\n > [!Note]\n> You need to setup backend locally and create superuser and login with it \n\nSteps to reproduce the behavior:\n\n1. Login as Admin (Superuser)\n2. Click on Admin Dashboard on top right corner\n3. See the error for both on md screen (use responsive browser tool)\n\n**Expected behavior**\nswitch to use Table view for medium and large screen and card view only for smaller screen\n\n\n**Screenshots**\n\n\u003Cimg width=\"1440\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8cabaef5-f7cb-4fd2-8c98-d40d339dcf4c\" />\n\n**Desktop (please complete the following information):**\n\n- OS: macOS\n- Browser: ARC \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",[],12695,"Switch to use Table View for Questionnaire and ValueSet Listing Page for medium screen","2025-06-23T14:34:08Z","https://github.com/ohcnetwork/care_fe/issues/12695",0.7783379,{"description":3053,"labels":3054,"number":3055,"owner":3029,"repository":3030,"state":3056,"title":3057,"updated_at":3058,"url":3059,"score":3060},"**Describe the bug**\nThere is no existing Cypress test case that verifies login should fail when leading whitespaces are present in the username and/or password fields. This scenario should be covered in the test suite to ensure validation is handled properly and consistently.(e.g., \" doctor_4_1 \", \" pass@123\").\n\n**To Reproduce**\n\nSteps to manually test and observe the missing validation in automation:\n1. Go to the login page\n2. Enter a valid username with a leading space, (e.g., \" administrator_2_0 \") \n3. Enter a valid password with a leading space, (e.g., \" Coronasafe@123 \")\n4. Click on the login button\n5. Login should fail, but currently, this is not covered in Cypress (It passed and opened dashbaord)\n\n\n**Expected behavior**\nLogin should not proceed when there are leading whitespaces in the username or password input. The test should confirm that:\n\n- An error message is shown\n- No login token/session is stored\n- User stays on the login page\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/2d5f0537-4578-4222-bbb8-249e0f76b7b3\n\n**Desktop:**\n\nOS: [Windows 11]\nBrowser [Chrome]\nVersion [138.0.7204.184 (Official Build) (64-bit)]\n\n**Smartphone (please complete the following information):**\n\n- Device: NA\n- OS: NA\n- Browser: NA\n- Version: NA\n\n**Additional context**\nThis edge case was identified during manual testing. It is recommended to include this test using Page Object Model in the existing login test file. Follow CARE guidelines:\n\n- Use reusable functions/components\n- Use `cy.intercept()` if needed\n- Avoid hardcoded waits\n- Use data-testid or id selectors \n\n✅ QA Suggestion:\n\nSuggested Test Case Name:\nshould NOT allow login with leading/trailing spaces in username or password\n\nDescription:\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\n- Login fails (user is not redirected to /dashboard)\n- An appropriate error message is shown (e.g., “Invalid credentials”)\n\nLocation to add the test:\ncare_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",[],13228,"closed","[Cypress] Add test case to prevent login with leading whitespaces in username and password","2025-08-04T04:10:50Z","https://github.com/ohcnetwork/care_fe/issues/13228",0.6174021,{"description":3062,"labels":3063,"number":3067,"owner":3029,"repository":3030,"state":3056,"title":3068,"updated_at":3069,"url":3070,"score":3071},"**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",[3064],{"name":3065,"color":3066},"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.6743873,{"description":3073,"labels":3074,"number":3075,"owner":3029,"repository":3030,"state":3056,"title":3076,"updated_at":3077,"url":3078,"score":3079},"**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.68232757,{"description":3081,"labels":3082,"number":3083,"owner":3029,"repository":3030,"state":3056,"title":3084,"updated_at":3085,"url":3086,"score":3087},"**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.7000699,{"description":3089,"labels":3090,"number":3091,"owner":3029,"repository":3030,"state":3056,"title":3092,"updated_at":3093,"url":3094,"score":3095},"**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.7055913,{"description":3097,"labels":3098,"number":3099,"owner":3029,"repository":3030,"state":3056,"title":3100,"updated_at":3101,"url":3102,"score":3103},"**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.7318238,{"description":3105,"labels":3106,"number":3107,"owner":3029,"repository":3030,"state":3056,"title":3108,"updated_at":3109,"url":3110,"score":3111},"**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.7348726,["Reactive",3113],{},["Set"],["ShallowReactive",3116],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqQkaQXYgth-kIVWKhFU7vjh7FnVlBaMc-nQUoD_4zeg":-1},"/ohcnetwork/care_fe/13226"]