\n\n\u003Cimg width=\"800\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/10454c54-243c-4d2d-b0be-f8d9ac8b010e\" />\n\nApart from that, answers are all text based, rather than being based on the type of the dependent question.\n\nTasks\n\n- [ ] Convert the enable when question link id input box (highlighted in dark blue) to a drop down\n- [ ] Said drop down should be populated with link Ids of other questions + question text.\n - Don't include questions of type structured/display\n - structured need to be handled separately in future (cc: Aravind).\n - So in the screenshot 2, dropdown should contain 1. nihal as a possible option.\n- [ ] Convert the answer text input (highlighted in light blue) to drop down for:\n - should be dependent on the choice from question link drop down\n - boolean and choice types\n - maintain text input for other types\n\nMake sure existing functionality works as is.\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",[],12448,"Modify Enable When UI For Questionnaires","2025-05-29T07:09:54Z","https://github.com/ohcnetwork/care_fe/issues/12448",0.78578234,{"description":2896,"labels":2897,"number":2904,"owner":2872,"repository":2873,"state":2874,"title":2905,"updated_at":2906,"url":2907,"score":2908},"**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",[2898,2901],{"name":2899,"color":2900},"question","d876e3",{"name":2902,"color":2903},"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.78813076,{"description":2910,"labels":2911,"number":2912,"owner":2872,"repository":2873,"state":2874,"title":2913,"updated_at":2914,"url":2915,"score":2916},"**Is your feature request related to a problem? Please describe.**\nCurrently, when conditional logic is applied to a choice-based question that allows multiple selections, only the first selected option is considered for triggering conditions. Additional selected options are ignored, resulting in incorrect visibility or behavior of dependent questions.\n\n\n**Describe the solution you'd like**\n1. Create a choice-type question with multiple select enabled.\n2. Define conditional logic on a dependent question (e.g., show if Option A or Option B is selected).\n3. Fill the form and select multiple options.\n4. Observe that only the first selected option triggers conditions; others have no effect.\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",[],12551,"Conditional Logic Fails for Multiple Selected Choices in Choice-Based Questions","2025-06-09T09:27:48Z","https://github.com/ohcnetwork/care_fe/issues/12551",0.7936986,{"description":2918,"labels":2919,"number":2920,"owner":2872,"repository":2873,"state":2874,"title":2921,"updated_at":2922,"url":2923,"score":2924},"**Describe the bug**\nIn a questionnaire with dependent choice-based questions, if a parent question is edited, the child question's options do not update accordingly during form filling. This leads to stale or incorrect options being shown to the user.\n\n**To Reproduce**\nIn a questionnaire with conditional question, try changing the option of the parent question and check the conditional follow up question. It remains same. \n\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n\n**Expected behavior**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\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",[],12549,"Choice Options Do Not Update When Parent Question is Edited","2025-06-09T09:22:10Z","https://github.com/ohcnetwork/care_fe/issues/12549",0.79864,{"description":2926,"labels":2927,"number":2928,"owner":2872,"repository":2873,"state":2874,"title":2929,"updated_at":2930,"url":2931,"score":2932},"**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.8064605,{"description":2934,"labels":2935,"number":2936,"owner":2872,"repository":2873,"state":2874,"title":2937,"updated_at":2938,"url":2939,"score":2940},"**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",[],12543,"Enhance Choice Question Type with Sorting, Numbering, and Reordering Features","2025-06-09T07:31:41Z","https://github.com/ohcnetwork/care_fe/issues/12543",0.80972886,{"description":2942,"labels":2943,"number":2946,"owner":2872,"repository":2873,"state":2947,"title":2948,"updated_at":2949,"url":2950,"score":2951},"**Describe the bug**\nIn the Questionnaire form, when a question type is set to Boolean (used for simple Yes/No questions), the \"Enable When\" conditional logic does not work as expected. Dependent questions that should appear based on the Boolean answer do not show, even when the condition is met.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Create a Questionnaire, question with type boolean\n2. Create 2nd question with \"Enable when conditions\"\n3. Save it, test it.\n4. See error\n\n**Expected behavior**\nDependent questions should appear or be enabled when the Boolean question evaluates to the specified condition.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/350ad3e5-0c04-46cd-b537-efabbac07ad6\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",[2944,2945],{"name":2899,"color":2900},{"name":2902,"color":2903},12437,"closed","\"Enable When\" Logic Not Working for Boolean Question Type in Questionnaire","2025-05-29T04:09:42Z","https://github.com/ohcnetwork/care_fe/issues/12437",0.76937306,{"description":2953,"labels":2954,"number":2958,"owner":2872,"repository":2873,"state":2947,"title":2959,"updated_at":2960,"url":2961,"score":2962},"Allow users to import questionnaires from a URL, this will enable us to sync questionnaire across instances. \n\nGiven a URL, the we should fetch the data and use our regular API’s to create the questionnaire. \n\nThe BE will have support to store the links \n\nAlso add an option to sync questionnaires, user will have a sync button that can be used to refresh the questionnaire data from the source. \n\n---\nBlocked as it required BE changes",[2955],{"name":2956,"color":2957},"blocked","e50620",11493,"FE: Allow users to import Questionnaire from URL","2025-06-04T01:28:40Z","https://github.com/ohcnetwork/care_fe/issues/11493",0.7755456,["Reactive",2964],{},["Set"],["ShallowReactive",2967],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f-J1yeEglLu74BAe-x2pkg3hlAjOxM3O9FP1icVuJ8V4":-1},"/ohcnetwork/care_fe/12527"]