\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",[],12097,"ohcnetwork","care_fe","open","Sidebar Active Tab Highlight Issues in Expanded and Nested Views","2025-08-02T09:20:36Z","https://github.com/ohcnetwork/care_fe/issues/12097",0.79515785,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**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.81104136,{"description":3188,"labels":3189,"number":3199,"owner":3172,"repository":3173,"state":3174,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### Description\nDesign and document a Breadcrumb navigation component for the Design System. \n\nThe breadcrumb should:\n1. Show the user’s current location within the app’s hierarchy.\n2. Allow quick navigation back to parent levels.\n3. Adapt to different screen sizes with responsive truncation/collapse patterns.\n\n### Design Requirements\n**Structure:**\n- Root → Section → Subsection → Current Page\n- Last item should indicate the current page (non-clickable).\n\n**States:**\n- Default\n- Hover / Focus\n- Active (link with underline)\n- Current page (disabled state styling)\n\n**Responsive**\n- On smaller screens, collapse middle items to an ellipsis\n- Provide tooltip or expanded view on click/hover for hidden paths.\n\n**Separators**\n- Use chevron (›) or slash (/)\n- Ensure consistent spacing\n\n**Icon Support**\n- Optional icon before first breadcrumb item for context (e.g., Home icon)\n\n**Accessibility Requirements**\n- Use nav with aria-label=\"Breadcrumb\"\n- Mark current page with aria-current=\"page\"\n- Ensure keyboard navigation works for all breadcrumb links.\n\n**Checklist**\n- [ ] Create breadcrumb component in the Design System library\n- [ ] Include size variations (if required.)\n- [ ] Add responsive behavior mockups (desktop & mobile)\n- [ ] Add usage guidelines in Figma page\n- [ ] Add accessibility notes (aria attributes, focus states)\n- [ ] Attach dev-ready Figma link in this issue",[3190,3193,3196],{"name":3191,"color":3192},"Design","0052cc",{"name":3194,"color":3195},"UI Component","fef2c0",{"name":3197,"color":3198},"Design System","fbca04",13348,"Add Breadcrumb Component — Design, Usage Guidelines & Accessibility","2025-08-12T10:17:03Z","https://github.com/ohcnetwork/care_fe/issues/13348",0.8143891,{"description":3205,"labels":3206,"number":3207,"owner":3172,"repository":3173,"state":3174,"title":3208,"updated_at":3209,"url":3210,"score":3211},"Description:\nWhile checking the bed layout for a location, the bed order is displayed in reverse. For example, in an ICU with 30 beds, the first view shows beds from 30 down to 20 instead of starting from 1 upwards.\n\nSteps to Reproduce:\n\nClick on a location.\n\nClick on a ward (e.g., 10-bed ICU).\n\nNotice that the beds are listed starting from the last bed number instead of the first.\n\nCurrent Behavior:\n\nBed list is ordered last-to-first.\n\nExample: ICU with 30 beds shows 30–20 on the first screen.\n\nExpected Behavior:\n\nBed list should start from the first bed (e.g., 1–10, then 11–20, and so on).\n\nThis will make it intuitive for users who usually admit patients from the first beds.\n\nImpact:\n\nUsers have to navigate to the last page to find the first beds, which slows down workflow.\n\nIn emergency situations, this creates unnecessary delays in locating and admitting patients.\n\nSuggested Fix:\n\nReverse the ordering so that bed view starts from the first bed number.",[],13822,"Bed view order shows in reverse (last-to-first) instead of first-to-last","2025-09-24T04:36:31Z","https://github.com/ohcnetwork/care_fe/issues/13822",0.8295305,{"description":3213,"labels":3214,"number":3215,"owner":3172,"repository":3173,"state":3174,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**Describe the bug**\nLocations are not displayed in the map even when it is visible in the list\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Locations\n2. Click on Maps\n3. See error\n\nIf not able to reproduce, create a facility with more than hundred locations in it.\n\n**Expected behavior**\nAll locations should be visible in the map\n\n**Screenshots**\n\n\u003Cimg width=\"1452\" height=\"899\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1e499867-7ff1-4381-99dd-0aa9c54513c8\" />\n\n\u003Cimg width=\"1452\" height=\"899\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f1798fb1-b5bc-47ab-ae9e-dfa55ab9ff2c\" />\n\n**Desktop (please complete the following information):**\n\n- iOS\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",[],13474,"Locations are not displayed in the map even when it is visible in the list","2025-08-22T11:52:02Z","https://github.com/ohcnetwork/care_fe/issues/13474",0.83621585,{"description":3221,"labels":3222,"number":3223,"owner":3172,"repository":3173,"state":3224,"title":3225,"updated_at":3226,"url":3227,"score":3228},"**Describe the bug**\n\"Each child in a list should have a unique 'key' prop\" appears in the browser console. The warning is specific to the component's render method in NavMain component.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any page with sidebar navigation\n2. Click on Open browser developer tools (F12)\n3. Check console\n4. See warning about missing key prop in list children\n\n**Expected behavior**\n1. No console warnings should appear\n2. Each child element in mapped lists should have a unique key prop\n3. React should properly track and update list items\n\n**Screenshots**\n\n\u003Cimg width=\"1894\" height=\"993\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/fee3037f-f122-47a0-a75a-25a74020f74a\" />\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 warning occurs in the sidebar navigation component where we're mapping over the Fragment wrapper (\u003C>) also needs a unique key since it's the direct child of the map function.\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",[],13551,"closed","Add unique 'key' prop to list items in NavMain component","2025-09-01T09:58:36Z","https://github.com/ohcnetwork/care_fe/issues/13551",0.7916104,{"description":3230,"labels":3231,"number":3232,"owner":3172,"repository":3173,"state":3224,"title":3233,"updated_at":3234,"url":3235,"score":3236},"## 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.7966805,{"description":3238,"labels":3239,"number":3243,"owner":3172,"repository":3173,"state":3224,"title":3244,"updated_at":3245,"url":3246,"score":3247},"**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",[3240],{"name":3241,"color":3242},"stale","688388",13621,"The tags in locations page are not proper","2025-09-30T11:00:03Z","https://github.com/ohcnetwork/care_fe/issues/13621",0.8001848,{"description":3249,"labels":3250,"number":3251,"owner":3172,"repository":3173,"state":3224,"title":3252,"updated_at":3253,"url":3254,"score":3255},"**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.80144274,{"description":3257,"labels":3258,"number":3263,"owner":3172,"repository":3173,"state":3224,"title":3264,"updated_at":3265,"url":3266,"score":3267},"**Is your feature request related to a problem? Please describe.**\nCurrently, there is no dashboard to provide a real-time, visual overview of bed availability at the facility (hospital) level. Hospital staff and administrators need a clear way to monitor which beds are available, occupied, or reserved in order to make efficient assignments and improve patient flow.\n\n**Describe the solution you'd like**\nDevelop a Facility Level Bed Availability Dashboard for Hospitals. This dashboard should:\n- Display a real-time overview of bed availability across all wards/units within a hospital facility.\n- Integrate with the existing locations API (already in use for assigning patients to available beds) to fetch up-to-date bed status.\n- Visually distinguish between available, occupied, and reserved beds, possibly with color coding or icons.\n- Allow staff to quickly identify which wards/units have the most/least capacity.\n- Optionally, provide filters for ward/unit, bed type, and availability status.\n\n**Describe alternatives you've considered**\n- Manual monitoring or spreadsheet tracking, which is not scalable or real-time.\n- External dashboard tools, but direct integration within the app using the locations API is preferred for data accuracy and seamless workflow.\n\n**Additional context**\n- The locations API is already leveraged for bed assignment workflows.\n- This dashboard will support operational efficiency and patient care.\n",[3259,3262],{"name":3260,"color":3261},"enhancement","a2eeef",{"name":3194,"color":3195},13756,"Build Facility Level Bed Availability Dashboard for Hospitals","2025-09-18T16:02:44Z","https://github.com/ohcnetwork/care_fe/issues/13756",0.8056032,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fs16QtyhB8hIsMXglXy3Gw3yIjWBFwJvhxTdj5eQhNtM":-1},"/ohcnetwork/care_fe/12451"]