\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,"closed","Make Buttons on User Dashboard responsive for mobile view","2025-08-05T05:55:59Z","https://github.com/ohcnetwork/care_fe/issues/13022",0.628279,{"description":3200,"labels":3201,"number":3211,"owner":3175,"repository":3176,"state":3194,"title":3212,"updated_at":3213,"url":3214,"score":3215},"**Is your feature request related to a problem? Please describe.**\nA clear and concise description of what the problem is. Ex. I'm always frustrated when [...]\n\n**Describe the solution you'd like**\nA clear and concise description of what you want to happen.\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",[3202,3205,3208],{"name":3203,"color":3204},"question","d876e3",{"name":3206,"color":3207},"stale","688388",{"name":3209,"color":3210},"needs-triage","ededed",12098,"Make SortIndex a Generic Reusable Component not just location specfic.","2025-07-30T09:45:14Z","https://github.com/ohcnetwork/care_fe/issues/12098",0.6310084,{"description":3217,"labels":3218,"number":3219,"owner":3175,"repository":3176,"state":3194,"title":3220,"updated_at":3221,"url":3222,"score":3223},"**Is your feature request related to a problem? Please describe.**\nThe buttons are all congested and sometimes fall outside the viewport on mobile. Even when they are within the viewport, they can be misaligned and look awkward.\n\n**Additional context**\n\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",[],12526,"Enhance the UI of the patient encounters file menu for mobile screens","2025-06-06T05:25:50Z","https://github.com/ohcnetwork/care_fe/issues/12526",0.65425324,{"description":3225,"labels":3226,"number":3228,"owner":3175,"repository":3176,"state":3194,"title":3229,"updated_at":3230,"url":3231,"score":3232},"**Is your feature request related to a problem? Please describe.**\nCurrently, comments are not sorted by newest first, making it hard to see recent feedback immediately.\n\n**Describe the solution you'd like**\nComments should be automatically sorted by newest first so that the most recent feedback appears at the top.\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**\n\nhttps://github.com/user-attachments/assets/c9e0a5b5-7628-4f0f-8200-6ee7afedefbe\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",[3227],{"name":3172,"color":3173},12409,"sort comments by newest first","2025-07-16T12:09:10Z","https://github.com/ohcnetwork/care_fe/issues/12409",0.654257,{"description":3234,"labels":3235,"number":3236,"owner":3175,"repository":3176,"state":3194,"title":3237,"updated_at":3238,"url":3239,"score":3240},"In appointments, would be easier to navigate if view patient profile button is available if there is an active encounter.\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",[],13156,"View Patient profile button in appointments","2025-07-31T10:59:14Z","https://github.com/ohcnetwork/care_fe/issues/13156",0.65443784,{"description":3242,"labels":3243,"number":3244,"owner":3175,"repository":3176,"state":3194,"title":3245,"updated_at":3246,"url":3247,"score":3248},"**Is your feature request related to a problem? Please describe.**\n- On Add Questionnaire page in encounter, there is no Back button provided for users to easily navigate to the previous page\n- Several pages in the system (e.g., Patient Detail, Encounter Detail, and similar detail views) do not provide a Back button for user navigation. This forces users to rely on the browser’s back button, which is not intuitive and may break the expected navigation flow.\n\n**Describe the solution you'd like**\nA Back button should be available, allowing users to return to the previous screen\n\n** Screenshot\n\n\u003Cimg width=\"1889\" height=\"968\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f02e5b15-2436-43e9-9bd0-2f28ea6ba4be\" />\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",[],13467,"Missing Back Button on Add Questionnaire page","2025-08-25T14:28:00Z","https://github.com/ohcnetwork/care_fe/issues/13467",0.6568674,{"description":3250,"labels":3251,"number":3255,"owner":3175,"repository":3176,"state":3194,"title":3256,"updated_at":3257,"url":3258,"score":3259},"**Is your feature request related to a problem? Please describe.**\nRedesign devices page and match with figma : \nhttps://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=11009-2716&p=f&t=pfIy5UyrlGkfeXv1-0\n\n**Describe the solution you'd like**\n\n\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",[3252],{"name":3253,"color":3254},"hold","e0acef",11401,"Redesign devices page","2025-07-23T10:31:23Z","https://github.com/ohcnetwork/care_fe/issues/11401",0.6575235,{"description":3200,"labels":3261,"number":3265,"owner":3175,"repository":3176,"state":3194,"title":3266,"updated_at":3267,"url":3268,"score":3269},[3262,3263,3264],{"name":3203,"color":3204},{"name":3206,"color":3207},{"name":3209,"color":3210},11969,"Add Request Letter support in the care 3.0","2025-08-13T06:27:26Z","https://github.com/ohcnetwork/care_fe/issues/11969",0.66055125,["Reactive",3271],{},["Set"],["ShallowReactive",3274],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLb9aIwrMEAK41dg4bHGRjO85Ah2pmwVeUB8bVWKwS5Q":-1},"/ohcnetwork/care_fe/13938"]