\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Go to any live encounter\n- go to medication request question\n- see the error for tablet screen size \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",[],13095,"Medication Request Question UI is breaking on tablet screens","2025-07-25T18:35:09Z","https://github.com/ohcnetwork/care_fe/issues/13095",0.69058025,{"description":3191,"labels":3192,"number":3193,"owner":3175,"repository":3176,"state":3177,"title":3194,"updated_at":3195,"url":3196,"score":3197},"**Is your feature request related to a problem? Please describe.**\nCurrently we use care Loading components in patient Search bar we can replace with TableSketelon loading\n\nhttps://github.com/user-attachments/assets/66be993b-4305-429f-8036-be11ff55c51e\n\n**Describe the solution you'd like**\nuse custom tableSketelon loading component\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",[],13813,"Replace Loading in the patient search bar with tableSketelon","2025-09-23T13:46:03Z","https://github.com/ohcnetwork/care_fe/issues/13813",0.6938731,{"description":3199,"labels":3200,"number":3201,"owner":3175,"repository":3176,"state":3177,"title":3202,"updated_at":3203,"url":3204,"score":3205},"**Is your feature request related to a problem? Please describe.**\nCurrently valueset preview option is only available while creating a valueset and not while viewing or editing\n\n**Describe the solution you'd like**\nImplement valueset preview feature for all modes\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",[],13680,"Valueset preview for all modes","2025-09-11T04:42:16Z","https://github.com/ohcnetwork/care_fe/issues/13680",0.6945628,{"description":3207,"labels":3208,"number":3212,"owner":3175,"repository":3176,"state":3177,"title":3213,"updated_at":3214,"url":3215,"score":3216},"**Is your feature request related to a problem? Please describe.**\n- In 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- 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\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",[3209],{"name":3210,"color":3211},"P1","519BFE",12550,"Highlight Active Section/Question Being Edited in Questionnaire Editor","2025-08-15T05:12:26Z","https://github.com/ohcnetwork/care_fe/issues/12550",0.69627017,{"description":3218,"labels":3219,"number":3229,"owner":3175,"repository":3176,"state":3230,"title":3231,"updated_at":3232,"url":3233,"score":3234},"**Is your feature request related to a problem? Please describe.**\nCurrently, `filter-tabs` is only being used for `ServiceRequestsList` and not in other places. Few components like `ToReceive`, `ToDispatch`, `PrescriptionQueue`, `ReceiveStock` etc. have filter tabs but do not use the reusable `filter-tabs` component\n\n**Describe the solution you'd like**\nUse the `filter-tabs` component instead of same piece of code\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",[3220,3223,3226],{"name":3221,"color":3222},"question","d876e3",{"name":3224,"color":3225},"stale","688388",{"name":3227,"color":3228},"needs-triage","ededed",13733,"closed","Use `filter-tabs` component throughout the codebase where required","2025-10-02T14:41:43Z","https://github.com/ohcnetwork/care_fe/issues/13733",0.60506064,{"description":3236,"labels":3237,"number":3241,"owner":3175,"repository":3176,"state":3230,"title":3242,"updated_at":3243,"url":3244,"score":3245},"**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",[3238,3239,3240],{"name":3221,"color":3222},{"name":3224,"color":3225},{"name":3227,"color":3228},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.6624266,{"description":3247,"labels":3248,"number":3251,"owner":3175,"repository":3176,"state":3230,"title":3252,"updated_at":3253,"url":3254,"score":3255},"**Is your feature request related to a problem? Please describe.**\n\nCurrently FileSubTab, DischargeSummarySubTab and FileQuestion are using pretty much the same code for the add_files dropdown menu. Its a lot of duplication\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",[3249,3250],{"name":3221,"color":3222},{"name":3227,"color":3228},13087,"Make add_files dropdown menu a reusable component","2025-07-25T13:11:04Z","https://github.com/ohcnetwork/care_fe/issues/13087",0.67213553,{"description":3257,"labels":3258,"number":3261,"owner":3175,"repository":3176,"state":3230,"title":3262,"updated_at":3263,"url":3264,"score":3265},"**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",[3259,3260],{"name":3221,"color":3222},{"name":3227,"color":3228},12225,"Add styling customization support for choice questions on questionnaire","2025-06-04T07:03:31Z","https://github.com/ohcnetwork/care_fe/issues/12225",0.68114173,{"description":3267,"labels":3268,"number":3269,"owner":3175,"repository":3176,"state":3230,"title":3270,"updated_at":3271,"url":3272,"score":3273},"**Is your feature request related to a problem? Please describe.**\nWhile selecting organizations when creating a questionnaire, there is no option to add all organizations or clear all\n\n**Describe the solution you'd like**\nAdd the feature for the user to select all or remove all organizations\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**\nImplement similar to other forms where suitable\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",[],13796,"Add `add-all` and `clear-all` feature while selecting organizations","2025-09-24T06:48:03Z","https://github.com/ohcnetwork/care_fe/issues/13796",0.6877825,["Reactive",3275],{},["Set"],["ShallowReactive",3278],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f_g5GX9L_m8oFdOIxdWRzNu4ndODE_YRmmeh3J1c6smA":-1},"/ohcnetwork/care_fe/13772"]