\n\u003Cimg width=\"1125\" height=\"869\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d37e7fa5-ce04-405a-8ed1-192fb4ae4ca5\" />",[],13062,"Responsive issue for Questionnaire Editor","2025-07-23T13:11:29Z","https://github.com/ohcnetwork/care_fe/issues/13062",0.7529683,{"description":3045,"labels":3046,"number":3047,"owner":3021,"repository":3022,"state":3023,"title":3048,"updated_at":3049,"url":3050,"score":3051},"**Describe the bug**\n\n- When filling structured questions like Diagnosis, Symptoms, etc., on mobile devices, some buttons are clipped and not fully visible. due to improper calculation of the view port\n- After submitting data in a structured questions in forms like the Community Nursing Form, instead of displaying the submitted response within the questionnaire, the interface scrolls to the next question.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to live encounter\n2. Click on add questionnaire and select community nurse form\n3. Submit a symptom or diagnosis \n4. See error\n\n**Expected behavior**\n\n- All UI elements, including buttons, should be fully visible and functional on mobile devices.\n- After submitting structured questionnaire responses, the submitted data should be displayed inline within the current question instead of moving to the next one automatically.\n\n**Screenshots**\n\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",[],12739,"Mobile UI issues with structured questionnaire input and submissions","2025-06-27T13:19:21Z","https://github.com/ohcnetwork/care_fe/issues/12739",0.75813663,{"description":3053,"labels":3054,"number":3061,"owner":3021,"repository":3022,"state":3023,"title":3062,"updated_at":3063,"url":3064,"score":3065},"**Is your feature request related to a problem? Please describe.**\nOn the questionnaire filling page, only the group-level question is shown initially. Sub-questions are hidden, making it difficult for users to see the full scope of the form. There's also no visual cue indicating which question the user is currently filling.\n\n\u003Cimg width=\"1901\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b35c90b7-efbe-490a-9e03-04ba824928dd\" />\n\n**Describe the solution you'd like**\n1. Display All Questions and Sub-Questions: Expand and show all questions and their respective sub-questions (if any) by default, so users can view the entire structure of the form.\n\n2. Highlight Active Question: As the user focuses on or begins typing in a question, highlight the current question block to give clear feedback about where they are in the form.\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",[3055,3058],{"name":3056,"color":3057},"question","d876e3",{"name":3059,"color":3060},"needs-triage","ededed",12548,"Improve Questionnaire Filling UX: Show All Questions and Highlight Current Question","2025-06-10T06:09:58Z","https://github.com/ohcnetwork/care_fe/issues/12548",0.7585089,{"description":3067,"labels":3068,"number":3075,"owner":3021,"repository":3022,"state":3076,"title":3077,"updated_at":3078,"url":3079,"score":3080},"**Describe the bug**\nDue to some recent changes in QuestinnaireEditor, the UI broke for mobile screen causing QuestionnaireProperties sticky on top for mobile which results scroll-y ui break and double rendering of questionnarie properties above questions and and after questions \n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/7c1dde7e-a825-4774-a50a-bde5a4d3c7ea\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",[3069,3072],{"name":3070,"color":3071},"bug","d73a4a",{"name":3073,"color":3074},"stale","688388",12721,"closed","Questionnaire Editor UI broke for mobile screen","2025-07-23T13:06:44Z","https://github.com/ohcnetwork/care_fe/issues/12721",0.6913339,{"description":3082,"labels":3083,"number":3086,"owner":3021,"repository":3022,"state":3076,"title":3087,"updated_at":3088,"url":3089,"score":3090},"**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",[3084,3085],{"name":3056,"color":3057},{"name":3059,"color":3060},12225,"Add styling customization support for choice questions on questionnaire","2025-06-04T07:03:31Z","https://github.com/ohcnetwork/care_fe/issues/12225",0.7122487,{"description":3092,"labels":3093,"number":3096,"owner":3021,"repository":3022,"state":3076,"title":3097,"updated_at":3098,"url":3099,"score":3100},"**Is your feature request related to a problem? Please describe.**\nCurrently, when creating a choice-type question in a questionnaire, managing the list of options becomes difficult if there are many entries. Now only option available is to move options up and down that to becomes difficult when number of options are more. \n\n**Describe the solution you'd like**\nAdd the following enhancements to the choice-type question editor:\n\n1. **Option Numbering:** Automatically number all options for easier reference and editing.\n2. Alphabetical Sorting: Add a one-click button to sort all options alphabetically (A-Z) and numerically .\n3. Reposition by Number: Provide a way to move an option to a specific position by entering the desired option number.\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",[3094,3095],{"name":3056,"color":3057},{"name":3059,"color":3060},12543,"Enhance Choice Question Type with Sorting, Numbering, and Reordering Features","2025-06-13T10:51:48Z","https://github.com/ohcnetwork/care_fe/issues/12543",0.71523976,{"description":3102,"labels":3103,"number":3106,"owner":3021,"repository":3022,"state":3076,"title":3107,"updated_at":3108,"url":3109,"score":3110},"**Describe the bug**\nThere is lack of responsiveness in some sections (Group Layout and Answer Options) of Questionnaire\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/admin/questionnaire/respiratory-support-/edit)\n2. Check different sections on Mobile View\n3. See error\n\n**Expected behavior**\nThere should be proper responsiveness for Mobile devices. Like we can add padding in Title of each field in 'Answer Options' section.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/01725d6b-9867-4b24-af1b-7d8aeaa25b51\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",[3104,3105],{"name":3056,"color":3057},{"name":3059,"color":3060},12486,"'Group Layout options' and 'Answer Options' of Questionnaire needs resposiveness","2025-06-19T05:30:36Z","https://github.com/ohcnetwork/care_fe/issues/12486",0.7224355,{"description":3112,"labels":3113,"number":3120,"owner":3021,"repository":3022,"state":3076,"title":3121,"updated_at":3122,"url":3123,"score":3124},"**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",[3114,3115,3118,3119],{"name":3056,"color":3057},{"name":3116,"color":3117},"discussion required","05EFF8",{"name":3073,"color":3074},{"name":3059,"color":3060},12175,"Improve radio button options on questionnaries","2025-06-20T14:59:43Z","https://github.com/ohcnetwork/care_fe/issues/12175",0.723274,["Reactive",3126],{},["Set"],["ShallowReactive",3129],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fNMxdgl7IStQOuvHbbOe0cGm4mdwP-V--s5zJGEcLADo":-1},"/ohcnetwork/care_fe/11857"]