\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.6373288,{"description":3029,"labels":3030,"number":3031,"owner":3021,"repository":3022,"state":3023,"title":3032,"updated_at":3033,"url":3034,"score":3035},"**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.6640925,{"description":3037,"labels":3038,"number":3039,"owner":3021,"repository":3022,"state":3023,"title":3040,"updated_at":3041,"url":3042,"score":3043},"**Is your feature request related to a problem? Please describe.**\n\nAdd drag & drop functionity for uploading files in FileSubTab, DischargeSummary and FileQuestion to improve UX.\n\n**Describe the solution you'd like**\n\nhttps://github.com/user-attachments/assets/b73d4a25-b5a3-42e6-b0fc-53a6af8acaa0\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",[],13090,"Feature Request: Add Drag & Drop Support for Uploading Files","2025-07-25T14:57:46Z","https://github.com/ohcnetwork/care_fe/issues/13090",0.6690163,{"description":3045,"labels":3046,"number":3047,"owner":3021,"repository":3022,"state":3023,"title":3048,"updated_at":3049,"url":3050,"score":3051},"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.6692645,{"description":3053,"labels":3054,"number":3055,"owner":3021,"repository":3022,"state":3023,"title":3056,"updated_at":3057,"url":3058,"score":3059},"**Is your feature request related to a problem? Please describe.**\nIn the questionnaire editor, when editing a specific section or question, there is no visual indication of which element is currently active. This makes it difficult to keep track of the editing context, especially in large or complex forms.\n\n**Describe the solution you'd like**\n- Visually highlight the section/question currently being edited (e.g., with a border, background color, or subtle glow).\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",[],12550,"Highlight Active Section/Question Being Edited in Questionnaire Editor","2025-06-09T09:23:51Z","https://github.com/ohcnetwork/care_fe/issues/12550",0.673294,{"description":3061,"labels":3062,"number":3063,"owner":3021,"repository":3022,"state":3023,"title":3064,"updated_at":3065,"url":3066,"score":3067},"Create a workflow that adds a new label (**Type Changes**) to any PRs that contains changes to files in src/types/**.\n\nAssigned to @parth-18-bansal\n\n**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",[],12980,"Github workflow: new label for type changes","2025-07-18T11:46:08Z","https://github.com/ohcnetwork/care_fe/issues/12980",0.674401,{"description":3069,"labels":3070,"number":3071,"owner":3021,"repository":3022,"state":3023,"title":3072,"updated_at":3073,"url":3074,"score":3075},"### Describe \n\nUpdate Select trigger, Input, Textarea, and DatePicker trigger components to use `border-gray-300` for borders to maintain visual consistency across CARE \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",[],13181,"Standardize input borders to border-gray-300","2025-07-31T11:44:52Z","https://github.com/ohcnetwork/care_fe/issues/13181",0.6750721,{"description":3077,"labels":3078,"number":3079,"owner":3021,"repository":3022,"state":3023,"title":3080,"updated_at":3081,"url":3082,"score":3083},"**Is your feature request related to a problem? Please describe.**\nAdd current Date and Time as defult value for date time questions\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",[],13141,"Add current Date and Time as defult value for date time questions","2025-07-29T11:32:45Z","https://github.com/ohcnetwork/care_fe/issues/13141",0.676254,{"description":3085,"labels":3086,"number":3090,"owner":3021,"repository":3022,"state":3091,"title":3092,"updated_at":3093,"url":3094,"score":3095},"**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",[3087],{"name":3088,"color":3089},"good first issue","7057ff",12409,"closed","sort comments by newest first","2025-07-16T12:09:10Z","https://github.com/ohcnetwork/care_fe/issues/12409",0.61233824,{"description":3097,"labels":3098,"number":3111,"owner":3021,"repository":3022,"state":3091,"title":3112,"updated_at":3113,"url":3114,"score":3115},"**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( Reqeusted by NCG doctor) \nImprove the radio button options on questionnaires. The current version on the users interface is not fully usefull on some scenarios. They are looking for a simple radio button options to select. \n\n**Describe the solution you'd like**\nA clear and concise description of what you want to happen.\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",[3099,3102,3105,3108],{"name":3100,"color":3101},"question","d876e3",{"name":3103,"color":3104},"discussion required","05EFF8",{"name":3106,"color":3107},"stale","688388",{"name":3109,"color":3110},"needs-triage","ededed",12175,"Improve radio button options on questionnaries","2025-06-20T14:59:43Z","https://github.com/ohcnetwork/care_fe/issues/12175",0.6291139,["Reactive",3117],{},["Set"],["ShallowReactive",3120],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fe60XOSRFzy4YdH1CFEEAku-0uuM6oSkCUDiCSpbnHnk":-1},"/ohcnetwork/care_fe/12098"]