\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**\n1. The invalid HTML can cause accessibility and SEO issues.\n\n2. This can be especially problematic in SSR environments due to DOM mismatch between server-rendered and hydrated versions.\n\n3. It also affects maintainability for contributors unaware of this subtle nesting rule.\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",[3190],{"name":3191,"color":3192},"stale","688388",13249,"closed","Hydration warning due to \u003Cdiv> inside \u003Cp> in ExpandableText component","2025-10-03T14:16:28Z","https://github.com/ohcnetwork/care_fe/issues/13249",0.64802617,{"description":3200,"labels":3201,"number":3202,"owner":3172,"repository":3173,"state":3194,"title":3203,"updated_at":3204,"url":3205,"score":3206},"**Describe the bug**\nIn the **Encounters → **Allergysection**, the UI is rendering a `\u003Ctr>` element directly inside a `\u003Cdiv>`. This is invalid HTML since `\u003Ctr>` must be a child of `\u003Ctable>`, `\u003Cthead>`, `\u003Ctbody>`, or `\u003Ctfoot>`. As a result, a hydration error is thrown in the console (`\u003Ctr> cannot be a child of \u003Cdiv>`).\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to the Encounters page.\n2. Add a allergy so that a row is rendered in the collapsible card.\n3. Open browser console → observe error:\n\n**Expected behavior**\n`\u003Ctr>` elements should only be used inside a proper `\u003Ctable>` structure.\n\n**Screenshots**\n\n\u003Cimg width=\"1887\" height=\"849\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/92d43507-0334-4452-acc6-6f8396e57552\" />\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",[],13668,"Invalid \u003Ctr> Placement Causing Hydration Error","2025-10-08T13:25:47Z","https://github.com/ohcnetwork/care_fe/issues/13668",0.6690128,{"description":3208,"labels":3209,"number":3211,"owner":3172,"repository":3173,"state":3194,"title":3212,"updated_at":3213,"url":3214,"score":3215},"Describe the bug\nHydration error occurs when accessing admin organization pages, causing React to throw hydration mismatch warnings and potentially breaking client-side functionality.\n\nTo Reproduce\nSteps to reproduce the behavior:\n\nGo to http://localhost:4000/admin/organizations/govt/6f89e366-263f-4154-ae1d-a53761ec53d4\n\nOpen browser developer console\n\nRefresh the page\n\nSee hydration error in console\n\nExpected behavior\nThe organization page should load without hydration errors, displaying the organization hierarchy and details correctly without any console warnings.\n\nScreenshots\n\n\u003Cimg width=\"2559\" height=\"1087\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/60942e84-452e-4018-9b9f-dd4c823301f8\" />\n\nConsole shows hydration mismatch error indicating server-rendered HTML doesn’t match client-side React output.\n\nDesktop (please complete the following information):\n\nOS: Windows\n\nBrowser: Chrome / Firefox / Safari\n\nVersion: Latest\n\nSmartphone (please complete the following information):\n\nDevice: Any mobile device\n\nOS: iOS / Android\n\nBrowser: Mobile browsers\n\nVersion: Latest\n\nAdditional context\nThe hydration error is caused by the expandedOrganizations state in AdminOrganizationList.tsx being initialized differently on server vs client.\n\nOn server-side, it renders with an empty Set.\n\nOn client-side, useEffect auto-expands parent organizations.\nThis mismatch leads to DOM structure differences during hydration.\n\n---\n\n🚨 **DO NOT EDIT BELOW THIS LINE** 🚨\n\n### Instructions for Requesting Assignment:\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",[3210],{"name":3191,"color":3192},13552,"Hydration error on admin organization pages","2025-09-30T06:01:44Z","https://github.com/ohcnetwork/care_fe/issues/13552",0.7132652,{"description":3217,"labels":3218,"number":3220,"owner":3172,"repository":3173,"state":3194,"title":3221,"updated_at":3222,"url":3223,"score":3224},"**Describe the bug**\nThe \"Has child locations\" tag is not properly enclosed in mobile view for locations page\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings'\n2. Click on Locations'\n3. Scroll down to location with the tag\n4. See error\n\n**Expected behavior**\nThe \"Has child locations\" tag should be properly visible similar to other tags\n\n**Screenshots**\n\n\u003Cimg width=\"466\" height=\"918\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/16b060f4-6eb1-44c0-ba69-699493f08455\" />\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",[3219],{"name":3191,"color":3192},13621,"The tags in locations page are not proper","2025-09-30T11:00:03Z","https://github.com/ohcnetwork/care_fe/issues/13621",0.7411631,{"description":3226,"labels":3227,"number":3228,"owner":3172,"repository":3173,"state":3194,"title":3229,"updated_at":3230,"url":3231,"score":3232},"**Describe the bug**\nThe Encounter Notes tab currently renders raw HTML/Markdown input directly, creating a security vulnerability.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Encounters' -> \"View Details\" -> \"Notes\".\n2. The HTML tags are rendered instead of being displayed as plain text\n\nhttps://github.com/user-attachments/assets/99117c9a-ca92-4abe-98c8-e5fb7d4d8c8c\n\n**Expected behavior**\nAll user input should be displayed as plain text only\n\nhttps://github.com/user-attachments/assets/4029ef35-b1b2-4401-91f4-a27cd44062a0\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",[],12574,"Disable HTML/Markdown Rendering in Message Component","2025-06-10T09:31:21Z","https://github.com/ohcnetwork/care_fe/issues/12574",0.7416275,{"description":3234,"labels":3235,"number":3242,"owner":3172,"repository":3173,"state":3194,"title":3243,"updated_at":3244,"url":3245,"score":3246},"**Describe the bug**\n\nDouble horizontal scrolling is there and the UI is not proper and consistent when description text is long. This is affecting user experience.\n\nhttps://github.com/user-attachments/assets/214743ca-9021-4d25-8d1a-ee63dd940b14\n\n**Expected behavior**\nDescription section should have responsiveness. We can add ExpandText component when text is more than the normal \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",[3236,3239],{"name":3237,"color":3238},"needs testing","bc1bf7",{"name":3240,"color":3241},"needs review","CCF900",12990,"Bug: Improve the UI for table of Tag Config Page","2025-08-19T06:47:46Z","https://github.com/ohcnetwork/care_fe/issues/12990",0.74485964,{"description":3248,"labels":3249,"number":3250,"owner":3172,"repository":3173,"state":3194,"title":3251,"updated_at":3252,"url":3253,"score":3254},"**Describe the bug**\nWhen entering text in the Archive dialog, Text should remain when closing via outside click or close button,\n but it should clear when clicking Cancel.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Encounters' -> \"View Encounters\" -> \"Files\"\n2. Click on 'Archive' and write some text.\n3. If the user clicks outside the dialog or the close button, the entered text should persist , \n but If the user clicks Cancel, the entered text should be cleared.\n\nhttps://github.com/user-attachments/assets/9b574503-471a-43e9-ad4e-d431b187211d\n\n**Expected behavior**\nThe text should be there if user clicks outside dialog or close button, but clicking cancel button it should clear.\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",[],13182,"Archive Dialog Text Persist on Cancel Button","2025-08-05T12:26:47Z","https://github.com/ohcnetwork/care_fe/issues/13182",0.7572915,{"description":3256,"labels":3257,"number":3264,"owner":3172,"repository":3173,"state":3194,"title":3265,"updated_at":3266,"url":3267,"score":3268},"**Description:** \n- In the Archive File dialog, when the user tries to archive a file without specifying a reason the HTML native validation appears.\n- The archive reason still persists on reopening the dialog.\n\nhttps://github.com/user-attachments/assets/60e6ad60-4218-4b6b-b5ab-bf3a7f7259e7\n\n**Expected Behavior:**\n- The error message should display when the textarea is empty and the user clicks Proceed instead of HTML native validation.\n- The error state (`archiveReasonError`) and textarea value (`archiveReason`) should reset when the dialog is closed.\n\n**Steps to Reproduce:**\n1. Open the **Archive File** dialog.\n2. Click **Proceed** without entering a reason.\n3. Observe the HTML yellow warning.\n4. Enter any reason.\n5. Click close icon.\n6. Reopen the dialog → the previous error message still appears.\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",[3258,3261],{"name":3259,"color":3260},"question","d876e3",{"name":3262,"color":3263},"needs-triage","ededed",13760,"Archive File Dialog: HTML validation overrides & Custom validation not cleared on close","2025-10-01T10:41:52Z","https://github.com/ohcnetwork/care_fe/issues/13760",0.7576702,["Reactive",3270],{},["Set"],["ShallowReactive",3273],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fo0BOo032OJQwIoNZhcL9JcZQ9wSUJyTwmw2_bFFlebA":-1},"/ohcnetwork/care_fe/13884"]