\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",[],13022,"ohcnetwork","care_fe","open","Make Buttons on User Dashboard responsive for mobile view","2025-07-21T18:35:02Z","https://github.com/ohcnetwork/care_fe/issues/13022",0.65770084,{"description":3027,"labels":3028,"number":3029,"owner":3019,"repository":3020,"state":3021,"title":3030,"updated_at":3031,"url":3032,"score":3033},"**Describe**\n\n\u003Cimg width=\"1440\" height=\"846\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/551d6d23-583c-49ae-b64b-206b02f1ff7e\" />\n\n\n**Expected behavior**\nRefer to resizable feature present for organization subtabs in Admin Dashboard 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",[],13057,"Add Resizable feature for Dept/team listing page","2025-07-23T10:06:36Z","https://github.com/ohcnetwork/care_fe/issues/13057",0.66333574,{"description":3035,"labels":3036,"number":3037,"owner":3019,"repository":3020,"state":3021,"title":3038,"updated_at":3039,"url":3040,"score":3041},"Redesign the facility organization selector according to new UI. Do ensure that existing functionality works.\n\nRefer to figma here: https://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=14787-31983&p=f\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",[],12792,"Facility Organization Selector Redesign","2025-07-04T07:18:01Z","https://github.com/ohcnetwork/care_fe/issues/12792",0.6744202,{"description":3043,"labels":3044,"number":3045,"owner":3019,"repository":3020,"state":3021,"title":3046,"updated_at":3047,"url":3048,"score":3049},"\n\n\u003Cimg width=\"1440\" height=\"897\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/725b6347-d7e4-433b-ae5e-b5b5415d4e72\" />\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Go to any live encounter\n- go to medication request question\n- see the error for tablet screen size \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",[],13095,"Medication Request Question UI is breaking on tablet screens","2025-07-25T18:35:09Z","https://github.com/ohcnetwork/care_fe/issues/13095",0.6958072,{"description":3051,"labels":3052,"number":3053,"owner":3019,"repository":3020,"state":3021,"title":3054,"updated_at":3055,"url":3056,"score":3057},"**Describe the bug**\nIn the newly created appointments view, the badge text spacing is not even. There is more space in the top compare to the bottom.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Appointments'\n2. See error\n\n**Expected behavior**\nThe y-space should be equal.\n\n**Screenshots**\n\n\u003Cimg width=\"1338\" height=\"406\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/41525077-93c0-48dc-a531-26fd89b29bf1\" />\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",[],13051,"Uneven Vertical Padding in Badge Text on Appointments View","2025-07-23T07:07:49Z","https://github.com/ohcnetwork/care_fe/issues/13051",0.6965851,{"description":3059,"labels":3060,"number":3061,"owner":3019,"repository":3020,"state":3021,"title":3062,"updated_at":3063,"url":3064,"score":3065},"**Describe the bug**\nRefer below screen recording , the alignment of button and text can be improve for mobile view like aligning button to centre and same for text divs \n\nhttps://github.com/user-attachments/assets/f4de8a4b-c71e-42de-bf23-9928bba217b0\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",[],13020,"Misalignment of Buttons and text for mobile view in User Profile page","2025-07-21T18:34:14Z","https://github.com/ohcnetwork/care_fe/issues/13020",0.70814914,{"description":3067,"labels":3068,"number":3069,"owner":3019,"repository":3020,"state":3021,"title":3070,"updated_at":3071,"url":3072,"score":3073},"**Describe the bug**\nIf we update a role with zero permissions, it shows saving but no changes will be made.\n\n\n**Expected behavior**\nAn error message asking to select at least one permission.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/bc89c9bc-1001-4adb-8e42-8443bc8ba1e3\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",[],12868,"RBAC role updation","2025-07-11T12:09:19Z","https://github.com/ohcnetwork/care_fe/issues/12868",0.7112885,{"description":3075,"labels":3076,"number":3077,"owner":3019,"repository":3020,"state":3078,"title":3079,"updated_at":3080,"url":3081,"score":3082},"**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,"closed","Redesign Departments List View like tabular design of location","2025-06-13T12:11:38Z","https://github.com/ohcnetwork/care_fe/issues/12474",0.6612602,{"description":3084,"labels":3085,"number":3086,"owner":3019,"repository":3020,"state":3078,"title":3087,"updated_at":3088,"url":3089,"score":3090},"**Describe the bug**\n\n\u003Cimg width=\"1440\" height=\"857\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/21f9218a-e03b-4d98-a1bd-4e92fc8b3dd0\" />\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",[],12886,"Fix console warning for Encounter view page","2025-07-14T15:07:11Z","https://github.com/ohcnetwork/care_fe/issues/12886",0.66601294,{"description":3092,"labels":3093,"number":3100,"owner":3019,"repository":3020,"state":3078,"title":3101,"updated_at":3102,"url":3103,"score":3104},"**Describe the bug**\nWhen viewing users with card view on departments page, the activity labels and buttons can overflow on smaller viewports.\n\n\n\n**To Reproduce**\n1. Go to Settings -> Departments \n2. Click on any department\n3. Click on the \"Users\" tab\n4. Adjust screen size to see error\n\n**Expected behavior**\nThe label should ideally shift down and be rendered below the user name when the screen size is smaller\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",[3094,3097],{"name":3095,"color":3096},"question","d876e3",{"name":3098,"color":3099},"needs-triage","ededed",12502,"Departments Page users cards can have overflowing UI","2025-06-17T13:48:42Z","https://github.com/ohcnetwork/care_fe/issues/12502",0.67964333,["Reactive",3106],{},["Set"],["ShallowReactive",3109],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fVDlraumBICwzmndh6m9nmpizZMbE3CztWKcgSWLxf0c":-1},"/ohcnetwork/care_fe/13042"]