\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Login as superadmin/admin\n- Go to Admin Dashboard\n- Go to Organization Tab\n- See the current UI \n\n\n\n**Expected Design**\n >[!TIP]\nRefer to desing for dept/team under any facility and match the exact design like table and card\n\nhttps://github.com/user-attachments/assets/1b63cc23-5d85-4477-b0c0-32776bb811bf\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",[],13042,"ohcnetwork","care_fe","open","Update the design for Goverance, Supplier and Roles under Organization tab","2025-07-28T05:44:38Z","https://github.com/ohcnetwork/care_fe/issues/13042",0.80932486,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### Description\nDesign and document an Avatar component to be added to the Design System with the following requirements:\n\n#### Shape Usage Guidelines\n\n1. Patients – Rounded rectangle avatar\n2. Healthcare staff – Circle avatar\n3. Facility – Squircle avatar (preferred, but check with dev.)\n\n> **Squircle Implementation Notes:**\n> Confirm with dev team if squircle can be implemented using SVG clip-path or CSS mask-image.\n> Ensure compatibility with mobile browsers.\n> If not feasible or reliable across browsers, fallback to rounded rectangle for Facility avatars.\n\n\n**Fallback Behavior**\nIf no profile image is available: Show two-letter initials (first letter of first & last name).\n\n**Checklist**\n- [ ] Avatar component added to the Design System with all three shape options.\n- [ ] Usage guidelines documented in Figma and design documentation.\n- [ ] Dev feasibility check for squircle completed and decision documented.\n- [ ] Link Figma component to the Design System library",[],13344,"Add Avatar Component – Shape Variations, Usage Guidelines & Fallbacks","2025-08-12T05:42:47Z","https://github.com/ohcnetwork/care_fe/issues/13344",0.8188713,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"Currently, in the Location Navigation Bar, when a parent entry is expanded, an API call is triggered recursively for each child location to determine whether the entry has further children and if an expand icon should be shown.\n\n**Problem Summary**\n- Not able to use has_children: true/false to decide whether to show the expand icon.\n - Reason: A location's child is a bed (beds should not be shown in the Location navbar).\n - The presence of beds causes has_children to be true, resulting in the expand icon being displayed even though no visible children exist in the Location navbar.",[],12451,"Optimize Location Navigation Bar: Avoid Redundant API Calls to Determine Expand Icon Visibility","2025-05-29T08:21:15Z","https://github.com/ohcnetwork/care_fe/issues/12451",0.8264504,{"description":3196,"labels":3197,"number":3204,"owner":3172,"repository":3173,"state":3205,"title":3206,"updated_at":3207,"url":3208,"score":3209},"**Description**\nA 'Back' button is needed on the Encounters page to improve user navigation and overall experience.\n\n**Problem**\nCurrently, there is no clear and consistent way for a user to return to the previous page from the Encounters page without relying on the browser's back button. This can be confusing for some users and may lead to a broken or unpredictable app flow.\n\n\u003Cimg width=\"2048\" height=\"1128\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7fe0e7d4-44c8-496e-8a9d-5c01f6acfa59\" />\n\n**Proposed Solution**\n\n1. Add a Medium (Height=32px) Tertiary 'Back' button with left arrow icon as leading icon to the top-left of the Encounters page header. Use an existing 'Back' button component exists in our design system.\n\n2. The button's action should navigate the user to the previous screen. For example, if a user came from the Patient's overview page, the 'Back' button should return them to that page.\n\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",[3198,3201],{"name":3199,"color":3200},"question","d876e3",{"name":3202,"color":3203},"needs-triage","ededed",13208,"closed","Feature: Add 'Back' button to Encounters page for improved navigation","2025-08-04T05:09:19Z","https://github.com/ohcnetwork/care_fe/issues/13208",0.80435586,{"description":3211,"labels":3212,"number":3213,"owner":3172,"repository":3173,"state":3205,"title":3214,"updated_at":3215,"url":3216,"score":3217},"**Is your feature request related to a problem? Please describe.**\nThere are few buttons that are just used for navigation, and are implemented with onClick navigate rather than Link\n\n**Describe the solution you'd like**\nUse Link convention\n\n**Describe alternatives you've considered**\nA clear and concise description of any alternative solutions or features you've considered.\n\n**Additional context**\nhttps://github.com/ohcnetwork/care_fe/pull/13935#discussion_r2398697779\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",[],13938,"Replace onClick navigate with Link for buttons that only navigate","2025-10-02T13:50:38Z","https://github.com/ohcnetwork/care_fe/issues/13938",0.8074919,{"description":3219,"labels":3220,"number":3226,"owner":3172,"repository":3173,"state":3205,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**Is your feature request related to a problem? Please describe.**\nCurrently, `filter-tabs` is only being used for `ServiceRequestsList` and not in other places. Few components like `ToReceive`, `ToDispatch`, `PrescriptionQueue`, `ReceiveStock` etc. have filter tabs but do not use the reusable `filter-tabs` component\n\n**Describe the solution you'd like**\nUse the `filter-tabs` component instead of same piece of code\n\n**Describe alternatives you've considered**\nA clear and concise description of any alternative solutions or features you've considered.\n\n**Additional context**\nAdd any other context or screenshots about the feature request here.\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",[3221,3222,3225],{"name":3199,"color":3200},{"name":3223,"color":3224},"stale","688388",{"name":3202,"color":3203},13733,"Use `filter-tabs` component throughout the codebase where required","2025-10-02T14:41:43Z","https://github.com/ohcnetwork/care_fe/issues/13733",0.8118787,{"description":3232,"labels":3233,"number":3234,"owner":3172,"repository":3173,"state":3205,"title":3235,"updated_at":3236,"url":3237,"score":3238},"**Describe**\nRedesign Departments List View like tabular design of location more cleaner and less space consuming making more departments to be shown on single page\n\nCurrent Dept Design \n\n\u003Cimg width=\"1166\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/12345786-feba-4891-a7dd-c71dea35e028\" />\n\nCurrent Location list Design\n\n\u003Cimg width=\"1166\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bee6246f-fbd0-4406-bea3-5100d8eaee59\" />\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",[],12474,"Redesign Departments List View like tabular design of location","2025-06-13T12:11:38Z","https://github.com/ohcnetwork/care_fe/issues/12474",0.8139592,{"description":3240,"labels":3241,"number":3242,"owner":3172,"repository":3173,"state":3205,"title":3243,"updated_at":3244,"url":3245,"score":3246},"**Description:** The patient Home appears congested. Key information, action buttons, and navigation tabs feel cramped, making the interface less user-friendly.\n\n\u003Cimg width=\"911\" height=\"401\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/620e581a-7f84-4f48-aa7c-36edc9fb7974\" />\n\n\n**Steps to Reproduce:**\n- Goto encounters from the sidebar\n- Select any patient\n- Navigate to Patient Home\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.",[],13838,"Enhancement of Patient Home Via Encounter","2025-09-26T06:10:23Z","https://github.com/ohcnetwork/care_fe/issues/13838",0.819112,{"description":3248,"labels":3249,"number":3253,"owner":3172,"repository":3173,"state":3205,"title":3254,"updated_at":3255,"url":3256,"score":3257},"The system now show all departments and team while an encounter is created, a better UX would be to default to all encounters they have access too, this would be our 90% of the workflow. \n\nFor the remaning 10% that involves inter-department transfers and connections, lets have a better UX in place",[3250,3251,3252],{"name":3199,"color":3200},{"name":3223,"color":3224},{"name":3202,"color":3203},11157,"Default to departments they have access to while creating an encounter","2025-08-13T05:57:58Z","https://github.com/ohcnetwork/care_fe/issues/11157",0.81953496,{"description":3259,"labels":3260,"number":3261,"owner":3172,"repository":3173,"state":3205,"title":3262,"updated_at":3263,"url":3264,"score":3265},"## 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.82219553,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2wgTeptMsMIXyPMhcDzlOyfS6KwnPquxkb3AnR6uJWo":-1},"/ohcnetwork/care_fe/13348"]