component inline without changing the URL. This can be confusing to the user because the URL still shows the protected route, but the content displayed is the login form.\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",[3190,3193],{"name":3191,"color":3192},"question","d876e3",{"name":3194,"color":3195},"needs-triage","ededed",12669,"closed","Redirect unauthenticated users to /login instead of rendering Login component in-place","2025-06-27T03:25:39Z","https://github.com/ohcnetwork/care_fe/issues/12669",0.8213021,{"description":3203,"labels":3204,"number":3205,"owner":3172,"repository":3173,"state":3197,"title":3206,"updated_at":3207,"url":3208,"score":3209},"**Describe the bug**\n`batch_requests` errors are not properly handled in the frontend causing page crashes\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings > Locations > Add Location > Create Multiple Beds Locations'\n2. If you don't have permission you'll see page crash\n\n**Screenshots**\n\n\n\n**Desktop (please complete the following information):**\n- Chrome on Windows 11\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",[],11641,"Permission Errors causing Page Crash","2025-07-30T08:18:44Z","https://github.com/ohcnetwork/care_fe/issues/11641",0.8219467,{"description":3211,"labels":3212,"number":3215,"owner":3172,"repository":3173,"state":3197,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**Describe the bug**\nThere is lack of responsiveness in some sections (Group Layout and Answer Options) of Questionnaire\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/admin/questionnaire/respiratory-support-/edit)\n2. Check different sections on Mobile View\n3. See error\n\n**Expected behavior**\nThere should be proper responsiveness for Mobile devices. Like we can add padding in Title of each field in 'Answer Options' section.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/01725d6b-9867-4b24-af1b-7d8aeaa25b51\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",[3213,3214],{"name":3191,"color":3192},{"name":3194,"color":3195},12486,"'Group Layout options' and 'Answer Options' of Questionnaire needs resposiveness","2025-06-19T05:30:36Z","https://github.com/ohcnetwork/care_fe/issues/12486",0.8230609,{"description":3221,"labels":3222,"number":3223,"owner":3172,"repository":3173,"state":3197,"title":3224,"updated_at":3225,"url":3226,"score":3227},"**Describe the bug**\nPrevent the creation of a Bed location unless a valid parent location is already selected. This ensures proper hierarchical structure and avoids orphaned Bed entries in the system.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to `Location` tab under setting nav\n2. Add on `Add Location` without selecting any parent location\n3. Create a bed type location\n4. See error \n\n**Expected behaviour**\nRemove the Bed form from form options when no parent is present\n\n> [!NOTE]\n> Expected behaviour could be different , this issue needs a review from core members\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/0bc62535-0af0-4bd3-97a0-4342e2566611\n\n\n> [!TIP]\n> GOOD FIRST ISSUE depends on expected behaviour decided 👍 \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",[],12664,"Restricting Creating Bed Location when no parent location is present","2025-06-19T19:11:09Z","https://github.com/ohcnetwork/care_fe/issues/12664",0.8240755,{"description":3229,"labels":3230,"number":3231,"owner":3172,"repository":3173,"state":3197,"title":3232,"updated_at":3233,"url":3234,"score":3235},"**Describe the bug**\nWe are able to create same devices multiple times. Since according to FHIR, the registered name for a Device does not have to be unique globally but we should add validations and make some fields required to solve this problem. \nId is generated by backend but we are not able to differentiate same registered name devices (as shown in the video).\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**\nWe should able to differentiate devices through id so that same registered name devices can be differentiated.\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/a2f2246b-7a11-4470-bcb0-8e4e04eb42db\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",[],12759,"Bug: Add validations to reduce redundancy for devices","2025-06-30T12:03:15Z","https://github.com/ohcnetwork/care_fe/issues/12759",0.824193,{"description":3237,"labels":3238,"number":3247,"owner":3172,"repository":3173,"state":3197,"title":3248,"updated_at":3249,"url":3250,"score":3251},"**Describe the bug**\nUser dropdown in the \"Assign User to Patient\" modal shows all users instead of filtering by current facility.\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**\nUser dropdown should display only users associated with the current facility.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/c7b9f064-f712-47cd-9188-9b28fa7c40b1\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",[3239,3240,3243,3246],{"name":3191,"color":3192},{"name":3241,"color":3242},"discussion required","05EFF8",{"name":3244,"color":3245},"stale","688388",{"name":3194,"color":3195},12408,"Restrict User Dropdown to Current Facility Users Only in Assign User to Patient Modal","2025-07-31T14:21:54Z","https://github.com/ohcnetwork/care_fe/issues/12408",0.8261306,{"description":3253,"labels":3254,"number":3256,"owner":3172,"repository":3173,"state":3197,"title":3257,"updated_at":3258,"url":3259,"score":3260},"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",[3255],{"name":3244,"color":3245},13552,"Hydration error on admin organization pages","2025-09-30T06:01:44Z","https://github.com/ohcnetwork/care_fe/issues/13552",0.8280302,{"description":3262,"labels":3263,"number":3264,"owner":3172,"repository":3173,"state":3197,"title":3265,"updated_at":3266,"url":3267,"score":3268},"**Describe the bug**\nCurrently, if user navigates to any `facility/{facilityId}` route through an organization, the `facilityId` is `undefined` and causes an error toast.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any Organization\n2. Click on patients\n3. Navigate to any patient\n4. Encounters Tab -> View Encounters\n5. Service Requests Tab / Consents -> View Consents / Diagnostic Report -> View Report all show error toast.\n\n**Expected behavior**\nThere should be no errors or undefined api calls made.\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\n\n\u003Cimg width=\"1470\" height=\"956\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9f53bdb3-7e53-45f6-8d46-6bd82d6ef10c\" />\n\n\u003Cimg width=\"1470\" height=\"956\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/da58658c-ac81-4016-a6ef-f811b74d6da2\" />\n\n\u003Cimg width=\"848\" height=\"164\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e7b825a1-2758-4b86-89e6-29f8f600e541\" />\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",[],13590,"Remove GET Facility api calls when navigating through Organization","2025-09-03T13:52:07Z","https://github.com/ohcnetwork/care_fe/issues/13590",0.8297056,["Reactive",3270],{},["Set"],["ShallowReactive",3273],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5xd3otYFEH0ouKj29lOmxWHkp8APw91WAN8Z3uTqGZE":-1},"/ohcnetwork/care_fe/12010"]