\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**\nThe issue is caused in FormField → Input usage:\n\n\u003CInput\n type=\"number\"\n min={1}\n defaultValue={1} // ❌ conflict\n {...field} // includes value + onChange\n/>\n\nThis passes both value and defaultValue, leading to the React error.\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",[],13574,"ohcnetwork","care_fe","open","Bug: Input field throws controlled/uncontrolled warning when using auto-fill slot duration toggle","2025-08-31T10:24:24Z","https://github.com/ohcnetwork/care_fe/issues/13574",0.76604885,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Describe the bug**\nDescription text in Specimen Definitions and Observation Definitions are not properly aligned in mobile view\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings'\n3. Click on 'Specimen Definitions'\n4. Scroll down to 'Definitions descriptions'\n5. See error\n**Expected behavior**\nShould be properly aligned and not be restricted to the width of the title of description\n\n**Screenshots**\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",[],13642,"Descriptions of Definitions are not properly aligned in mobile view","2025-09-07T07:57:57Z","https://github.com/ohcnetwork/care_fe/issues/13642",0.7735064,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\nWhile adding a charge item, the info text goes across the screen and is not readable by user\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**\nIt should be properly aligned in the screen and be readable\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: j7 max\n- OS: android \n- Browser chrome\n- Version latest\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",[],13658,"Info text not properly aligned in mobile view","2025-09-08T13:48:34Z","https://github.com/ohcnetwork/care_fe/issues/13658",0.7777777,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Describe**\nOn searching any location, if the location matches the search text expand the location tree upto search matches\n\nrefer to the video \n\nIn video, `Test br` should've got expanded since search matches its child location \n\nAdditionally, fix the focus state for the search input here \n\nhttps://github.com/user-attachments/assets/44dc107d-d185-4d02-9d61-470c5786d12a\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Go to any Facility\n- Go to Acitivity Definition form under setting tab\n- Click on Select location \n- Try to search a child location \n- see the error \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",[],13093,"Expand upto child location if search matches in Location select","2025-07-25T18:34:31Z","https://github.com/ohcnetwork/care_fe/issues/13093",0.7795623,{"description":3204,"labels":3205,"number":3209,"owner":3172,"repository":3173,"state":3210,"title":3211,"updated_at":3212,"url":3213,"score":3214},"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",[3206],{"name":3207,"color":3208},"stale","688388",13552,"closed","Hydration error on admin organization pages","2025-09-30T06:01:44Z","https://github.com/ohcnetwork/care_fe/issues/13552",0.63389236,{"description":3216,"labels":3217,"number":3218,"owner":3172,"repository":3173,"state":3210,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**Describe the bug**\nWhen using `AlertDialogDescription` in `DischargeConfirmationDialog.tsx`, the component renders a `\u003Cp>` tag by default. \nSince the children passed to it include multiple `\u003Cp>` tags and a `\u003Cul>`, this results in invalid HTML (`\u003Cp>` cannot contain another `\u003Cp>` or `\u003Cul>`). \nThis causes hydration errors\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Ecounters.\n2. Click on view encounters of person and click on update details.\n3. click on update Encounter and then click on Mark for discharge.\n4. See error in console\nDirect link for local development view: [click here ](http://localhost:4000/facility/f50f0b79-461f-4e17-a55a-3df9b757978a/patient/106a9452-b0ad-4729-a33c-df8c302b4f62/encounter/08af18c2-6347-4546-a904-ab97aeb39927/questionnaire/encounter)\n\n**Expected behavior**\nNo hydration error in console.\n\n**Screenshots**\n\n\u003Cimg width=\"1896\" height=\"996\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/892fa113-6ca2-4741-ad5d-bb74d70dc269\" />\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**\nThis issue occurs because AlertDialogPrimitive.Description renders a `\u003Cp>` by default.\nWhen multiple block elements (`\u003Cp>`, `\u003Cul>`) are provided as children, it generates invalid nested markup.\nA possible solution is to use asChild and render a `\u003Cdiv>` instead of `\u003Cp>`, allowing the children to include valid block elements.\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",[],13884,"Use asChild with AlertDialogDescription to prevent nested \u003Cp> tags and hydration errors","2025-10-01T09:13:56Z","https://github.com/ohcnetwork/care_fe/issues/13884",0.6416816,{"description":3224,"labels":3225,"number":3226,"owner":3172,"repository":3173,"state":3210,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**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.6615406,{"description":3232,"labels":3233,"number":3240,"owner":3172,"repository":3173,"state":3210,"title":3241,"updated_at":3242,"url":3243,"score":3244},"**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",[3234,3237],{"name":3235,"color":3236},"needs testing","bc1bf7",{"name":3238,"color":3239},"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.7357931,{"description":3246,"labels":3247,"number":3248,"owner":3172,"repository":3173,"state":3210,"title":3249,"updated_at":3250,"url":3251,"score":3252},"## Describe the bug\nWhen navigating to the organization page, React console shows a warning about missing key props in the navigation sidebar. The warning indicates that each child in a list should have a unique \"key\" prop, affecting the `SidebarMenu` component.\n\n## To Reproduce\nSteps to reproduce the behavior:\n1. Navigate to organization page (https://care.ohc.network/organization/5d5f30f5-8a0c-41c8-890f-3efcc816111f)\n2. Open browser developer console\n3. See the warning: \"Each child in a list should have a unique 'key' prop\"\n\n## Expected behavior\nThe navigation sidebar should render without any React key prop warnings in the console.\n\n## Video\n\nhttps://github.com/user-attachments/assets/fd4497a1-fa89-49f4-bf9d-d701ee9a0832\n\n## Desktop (please complete the following information):\n- OS: Windows 10\n- Browser: Chrome\n- Version: Latest\n\n## Smartphone (please complete the following information):\n- Device: [Not applicable]\n- OS: [Not applicable]\n- Browser: [Not applicable]\n- Version: [Not applicable]\n\n## Additional context\nThe issue occurs in the `NavMain` component where list items are being rendered without proper key props. This affects the React reconciliation process and could potentially impact performance.\n\n🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\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]\n\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.",[],12542,"Bug: React Key Prop Warning in Navigation Sidebar","2025-06-09T11:51:52Z","https://github.com/ohcnetwork/care_fe/issues/12542",0.749299,{"description":3254,"labels":3255,"number":3256,"owner":3172,"repository":3173,"state":3210,"title":3257,"updated_at":3258,"url":3259,"score":3260},"**Describe the bug**\nIn the Facility Details page, the Description section overflows horizontally on smaller screen sizes (e.g., mobile view). This happens even when the text content is valid and contains URLs or long sentences. It affects the overall readability and breaks the layout.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to the Facility Details page on a mobile device or simulate mobile view in dev tools.\n2. Scroll down to the Description section.\n3. Observe that long lines of text or URLs cause horizontal overflow.\n4. See error\n\n**Expected behavior**\nThe description text should wrap correctly and stay within the container boundaries without causing overflow on mobile screens.\n\n**Screenshots**\n**Current Behavior** \n\n\u003Cimg width=\"672\" height=\"701\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/06137104-dc0b-44a6-84ab-a56e68d81ebc\" />\n\n**Expected Behavior**:\n\n\u003Cimg width=\"679\" height=\"711\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5ae15825-bb04-45de-8f70-503ec968f7b1\" />\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",[],13152,"Description Text Overflows on Mobile View","2025-07-31T10:59:43Z","https://github.com/ohcnetwork/care_fe/issues/13152",0.74954814,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fwhXaiVTTbuNI-C3Std5Mkxc4Kpqfs5IRI0BaZn6Y-I0":-1},"/ohcnetwork/care_fe/13249"]