\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,"Make Buttons on User Dashboard responsive for mobile view","2025-07-21T18:35:02Z","https://github.com/ohcnetwork/care_fe/issues/13022",0.6650558,{"description":3051,"labels":3052,"number":3053,"owner":3019,"repository":3020,"state":3021,"title":3054,"updated_at":3055,"url":3056,"score":3057},"**Here are some of my suggestions for improving Questionnnaire Importing**\n\n1. Currently, after clicking \"Import from URL\" in /admin/questionnaire, the flow is:\n- Dialog opens with an \"Import\" button\n- Paste link → Click \"Import\" → Toast shows \"Questionnaire Imported Successfully\"\n- New dialog opens with \"Import Form\" button\n- Click again → Toast shows \"Questionnaire Imported Successfully\"\n\nSuggested Improvement:\n- Change the first button label from \"Import\" to \"Continue\" after pasting the link\n- Show the success toast after final confirmation in the second dialog (\"Import Form\")\n\nLike this:\n\nhttps://github.com/user-attachments/assets/ed1dfdf7-8a3f-45a2-9908-84cf2c31de17\n\n2. Keyboard Support\n- Enhance UX by triggering \"Continue\" and \"Import Form\" buttons when pressing Enter.\n\n3. File Size Limit\n- Implement a 10 MB limit for JSON files to prevent performance issues.\n\n4. Download Button State\n- Disable the download button while the questionnaire is updating to avoid conflicts.\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",[],12582,"Suggestions for Improving Questionnaire Importing","2025-06-10T11:06:30Z","https://github.com/ohcnetwork/care_fe/issues/12582",0.68823147,{"description":3059,"labels":3060,"number":3061,"owner":3019,"repository":3020,"state":3021,"title":3062,"updated_at":3063,"url":3064,"score":3065},"**Describe the bug**\n\nWhen the same questionnaire (e.g., Community Nurse Form) is added more than once to a patient encounter, the second instance does not appear or is not rendered.\n\n**To Reproduce**\n\n1. Navigate to a patient encounter.\n2. Click on \"Add Questionnaire\".\n3. Select and add the Community Nurse Form.\n4. While filling the form, scroll to the bottom and click \"Add Questionnaire\" again.\n5. Attempt to add the Community Nurse Form once more.\n6. Observe that the second community nurse form does not appear.\n\n**Expected behavior**\n\nThe system should allow adding multiple copies of the same questionnaire within a single patient encounter if added more than once.\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",[],12757,"Unable to Add Same Questionnaire Multiple Times in patient encounter","2025-06-30T08:39:00Z","https://github.com/ohcnetwork/care_fe/issues/12757",0.70244616,{"description":3067,"labels":3068,"number":3072,"owner":3019,"repository":3020,"state":3073,"title":3074,"updated_at":3075,"url":3076,"score":3077},"**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",[3069],{"name":3070,"color":3071},"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.653135,{"description":3079,"labels":3080,"number":3093,"owner":3019,"repository":3020,"state":3073,"title":3094,"updated_at":3095,"url":3096,"score":3097},"**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",[3081,3084,3087,3090],{"name":3082,"color":3083},"question","d876e3",{"name":3085,"color":3086},"discussion required","05EFF8",{"name":3088,"color":3089},"stale","688388",{"name":3091,"color":3092},"needs-triage","ededed",12175,"Improve radio button options on questionnaries","2025-06-20T14:59:43Z","https://github.com/ohcnetwork/care_fe/issues/12175",0.65452844,{"description":3099,"labels":3100,"number":3101,"owner":3019,"repository":3020,"state":3073,"title":3102,"updated_at":3103,"url":3104,"score":3105},"**Is your feature request related to a problem? Please describe.**\n\nCurrently, the layout of questionnaire responses on the patient dashboard looks clumpy and difficult to read through. ( requested by NCG doctors)\n\n\u003Cimg width=\"518\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e9c68069-7991-4f9a-ba3a-383fedbb9bc4\" />\n\n**Describe the solution you'd like**\n\nThe question titles should be on the left and the responses should come on the right-hand side. refer the below picture\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**\nDoctors use the above mentioned section to understand the patient's clinical condition. this acts as a case summary for the patient. So the clubbed together format doesnt help them to asses it easily. Titles on left and contents on right format makes it better for the doctors to read through. \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",[],12223,"Improve the questionnaire visualisation on patient dashboard","2025-06-09T06:41:24Z","https://github.com/ohcnetwork/care_fe/issues/12223",0.6593451,{"description":3107,"labels":3108,"number":3111,"owner":3019,"repository":3020,"state":3073,"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 [...]\nCurrently there is no styling options available to the choice options in the questionnaires. all the choice options are coming in one by one list. \n\n\u003Cimg width=\"535\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bf9eaa1b-92a0-411e-b2b9-d3379e9243cb\" />\n\n**Describe the solution you'd like**\nA clear and concise description of what you want to happen.\nThe styling option will allow users to select the choice options to come in horizontal view or vertical list etc.\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",[3109,3110],{"name":3082,"color":3083},{"name":3091,"color":3092},12225,"Add styling customization support for choice questions on questionnaire","2025-06-04T07:03:31Z","https://github.com/ohcnetwork/care_fe/issues/12225",0.6616567,["Reactive",3117],{},["Set"],["ShallowReactive",3120],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fR2SbvUYx2fwl3LEtUOK4UtRbNZZRhiqWQz_SwvyZEbQ":-1},"/ohcnetwork/care_fe/12548"]