\n\n\u003Cimg width=\"215\" height=\"92\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bfabfadd-5e19-4442-9b01-59ea11beacac\" />\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patients\n2. Select any patient and update vitals and files\n3. Select the discharge summary and generate\n4. See error\n\n**Expected behavior**\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",[],13072,"Unnecessary details are reflecting on Discharge Summary","2025-07-24T12:54:43Z","https://github.com/ohcnetwork/care_fe/issues/13072",0.7364701,{"description":3058,"labels":3059,"number":3060,"owner":3026,"repository":3027,"state":3028,"title":3061,"updated_at":3062,"url":3063,"score":3064},"**Describe the bug**\nThe voice recording progress bar fails to animate correctly during audio capture\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Encounters' -> \"Files\".\n2. Click on 'Add Files' -> \"Add audio\"\n3. See error after recording the voice , the voice progress bar always stays at the end instead of smoothly transitioning from the beginning.\n\nhttps://github.com/user-attachments/assets/319a2ad6-baf2-4df5-8db9-733fa00c459f\n\n**Expected behavior**\nThe progress bar’s movement should accurately reflect the elapsed recording time\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",[],13001,"Voice Recording Progress Bar Jumps to End Instead of Smoothly Filling","2025-07-20T16:32:32Z","https://github.com/ohcnetwork/care_fe/issues/13001",0.74789745,{"description":3066,"labels":3067,"number":3068,"owner":3026,"repository":3027,"state":3028,"title":3069,"updated_at":3070,"url":3071,"score":3072},"**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.7521373,{"description":3074,"labels":3075,"number":3076,"owner":3026,"repository":3027,"state":3028,"title":3077,"updated_at":3078,"url":3079,"score":3080},"**Describe the bug**\nThe current progress bar provides minimal visual feedback during file uploads.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n\n**Expected behavior**\nThe progress bar should have a modern, visually clear design with smooth animations and clear indicators to enhance the user experience during file uploads.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/30d31928-62fd-40e9-8b93-ad23e1494e92\n\nExpected\n\nhttps://github.com/user-attachments/assets/3846870e-d645-427d-81aa-421d9ab2115a\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",[],12497,"Enhance Progress Bar UI/UX for Better Visual Feedback During File Upload","2025-06-03T08:00:54Z","https://github.com/ohcnetwork/care_fe/issues/12497",0.7694185,{"description":3082,"labels":3083,"number":3084,"owner":3026,"repository":3027,"state":3085,"title":3086,"updated_at":3087,"url":3088,"score":3089},"**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.66181666,{"description":3091,"labels":3092,"number":3093,"owner":3026,"repository":3027,"state":3085,"title":3094,"updated_at":3095,"url":3096,"score":3097},"**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.6787408,{"description":3099,"labels":3100,"number":3101,"owner":3026,"repository":3027,"state":3085,"title":3102,"updated_at":3103,"url":3104,"score":3105},"**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.7206347,["Reactive",3107],{},["Set"],["ShallowReactive",3110],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgZmJyNbOyYW1LlNJK34jJ_a8Mwm_yD3IGolsuMBFVNE":-1},"/ohcnetwork/care_fe/13100"]