\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",[],13711,"ohcnetwork","care_fe","closed","Password input fields missing autocomplete attributes","2025-10-01T07:27:03Z","https://github.com/ohcnetwork/care_fe/issues/13711",0.5569905,{"description":3180,"labels":3181,"number":3188,"owner":3172,"repository":3173,"state":3174,"title":3189,"updated_at":3190,"url":3191,"score":3192},"**Describe the bug**\nOn the User Information page, when editing the password fields (Current Password, New Password, and Confirm New Password), I noticed that two eye icons appear inside the input field, one from our code and one injected by the browser (likely default). Both perform the same toggle, but it looks redundant and might confuse users.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Navigate to the User Information page.\n2. Go to the Reset Password section.\n3. Start typing into any of the password fields (Current Password, New Password, or Confirm New Password).\n4. Observe that two \"eye\" icons appear for toggling password visibility.\n\n**Expected behavior**\nOnly one visibility toggle icon should appear per password field, which toggles the visibility of that specific field.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/66d6b3b8-c118-4f01-ab35-4ede3b442a0a\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",[3182,3185],{"name":3183,"color":3184},"question","d876e3",{"name":3186,"color":3187},"needs-triage","ededed",12877,"Duplicate Password Visibility Toggle Icons Appearing","2025-07-14T08:12:40Z","https://github.com/ohcnetwork/care_fe/issues/12877",0.7114714,{"description":3194,"labels":3195,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**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",[3196,3197],{"name":3183,"color":3184},{"name":3186,"color":3187},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.7177267,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3174,"title":3207,"updated_at":3208,"url":3209,"score":3210},"**Describe the bug**\nFix the nested button error in autocomplete. One approach would be to convert parent button to div and then modify it's styling, though you are welcome to try other approaches.\n\nKeep in mind, existing functionality should be maintained (ensure that input is highlighted on form error). Autocomplete is used in a lot of places.\n\n**Screenshots**\n\n\u003Cimg width=\"1027\" height=\"826\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/4236c702-6cc9-49ce-8656-29a003ac5114\" />\n\nAssigned to @Tanuj1718 \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",[],13345,"Autocomplete Nested Button Error","2025-08-19T12:06:45Z","https://github.com/ohcnetwork/care_fe/issues/13345",0.7198646,{"description":3212,"labels":3213,"number":3214,"owner":3172,"repository":3173,"state":3174,"title":3215,"updated_at":3216,"url":3217,"score":3218},"**Describe the bug**\nThe validation messages for the \"Password\" and \"Confirm Password\" fields are not showing.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Department'.\n2. Click on 'Users' -> \"Add users\".\n3. See error, the validation message for password and confirm password is not showing.\n\nhttps://github.com/user-attachments/assets/ee0e9127-5a26-4867-93c4-eb135702e6b4\n\n**Expected behavior**\nWhen the form is submitted validation messages should appear directly below input fields.\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",[],12820,"Password validation messages are not displayed on the Add User form","2025-07-10T06:41:05Z","https://github.com/ohcnetwork/care_fe/issues/12820",0.73164654,{"description":3220,"labels":3221,"number":3224,"owner":3172,"repository":3173,"state":3174,"title":3225,"updated_at":3226,"url":3227,"score":3228},"**Describe the bug**\nWhen searching patients using the phone number option, the entered number persists in the input even after **clearing** it, switching to \"search by name,\" and then switching back to \"search by phone number.\" This causes confusion, as users expect a fresh input field after clearing or switching search modes\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patients Page\n2. Search by Phone number and then clear it\n3. Switch to search by name and then again switch to search by phone number\n4. See error\n\n**Expected behavior**\nWhen switching search types (e.g., from phone number to name and back), the input field should reflect the most recent state. If the field was cleared earlier, it should remain empty upon switching back.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/8e6740e7-f2b8-4a5a-ae24-19e4c6e3461b\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",[3222,3223],{"name":3183,"color":3184},{"name":3186,"color":3187},13144,"Search Input Retains Previous Phone Number After Switching Search Type","2025-07-30T02:18:15Z","https://github.com/ohcnetwork/care_fe/issues/13144",0.7398592,{"description":3230,"labels":3231,"number":3232,"owner":3172,"repository":3173,"state":3174,"title":3233,"updated_at":3234,"url":3235,"score":3236},"**Describe the bug**\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Create a questionnaire with type \"choice\" and option as ValueSet (select a ValueSet that isn't listed on the first page).\n2. Edit the Questionnaire\n3. See error\n\n**Expected behavior**\nThe Valuset should be visible while editing\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**\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",[],12625,"Valueset Missing from Search Field During Edit Questionnaire","2025-06-16T13:39:51Z","https://github.com/ohcnetwork/care_fe/issues/12625",0.74898374,{"description":3238,"labels":3239,"number":3242,"owner":3172,"repository":3173,"state":3174,"title":3243,"updated_at":3244,"url":3245,"score":3246},"**Describe the bug**\nA warning banner is displayed with the message:\nField required Missing: 'user'\neven though no action has been taken that should trigger this validation. This appears to be an unwanted warning on the Availability page.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to my schedule in Overview section.\n2. Click on the Availability page\n3. See error\n\n**Expected behavior**\nNo validation or missing field warning should be displayed by default when just navigating to the Availability tab. The page should load cleanly without error banners unless a required field is truly missing on a user-triggered action (e.g., saving a template without selecting a user).\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/b65229d7-ddda-44d7-a3a2-ab5e8dbadd43\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",[3240,3241],{"name":3183,"color":3184},{"name":3186,"color":3187},13790,"Unwanted Warning Missing:'user'","2025-09-29T13:45:38Z","https://github.com/ohcnetwork/care_fe/issues/13790",0.75172544,{"description":3248,"labels":3249,"number":3253,"owner":3172,"repository":3173,"state":3174,"title":3254,"updated_at":3255,"url":3256,"score":3257},"**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",[3250],{"name":3251,"color":3252},"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.7547026,{"description":3259,"labels":3260,"number":3263,"owner":3172,"repository":3173,"state":3174,"title":3264,"updated_at":3265,"url":3266,"score":3267},"**Describe the bug**\nThe Add Tag Config form has a bug where it requires a \"Slug\" field that is not visible, preventing submission.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings > Tag Config'\n2. Click on 'Add Tag Config'\n3. Add a name and submit\n4. See error\n\n**Expected behavior**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/aa9e12ab-ee58-4d3b-baab-ef0d3916d357\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",[3261,3262],{"name":3183,"color":3184},{"name":3186,"color":3187},13833,"Missing Required Field on \"Add Tag Config\" Form","2025-10-08T11:01:08Z","https://github.com/ohcnetwork/care_fe/issues/13833",0.75502944,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJ1qN34zDKSjbjbbO9suJYm9uDc3t4KPPkWEmUd9NtuE":-1},"/ohcnetwork/care_fe/12535"]