\n\nNavigate to the questionnaire submission page.\n\nFill in all fields with valid and required input.\n\nClick on the Submit button.\n\nObserve that a validation error is displayed on the UI.\n\nOpen DevTools (F12) → Go to the Network tab.\n\nCheck the failed API request related to the submission.\n\nNote:\n\nStatus shown in DevTools: 400 Bad Request\n\nAPI response body: contains a server error message with internal status 500\n\nExpected Behavior:\n\nThe questionnaire should submit successfully if all fields are valid. If there is a server-side failure, it should show an appropriate server error message.\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",[],12992,"ohcnetwork","care_fe","open","Shown validation error while submitting a questionnaire","2025-07-19T08:14:34Z","https://github.com/ohcnetwork/care_fe/issues/12992",0.70468086,{"description":3027,"labels":3028,"number":3029,"owner":3019,"repository":3020,"state":3021,"title":3030,"updated_at":3031,"url":3032,"score":3033},"**Describe the bug**\n\n- WHEN YOu fill all the data in the form and swap the selection for a field with an enable_when condition, the questionnaire is throwing an error upon submission\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",[],12810,"Questionnaire submission is failing for enable when condition","2025-07-07T10:19:06Z","https://github.com/ohcnetwork/care_fe/issues/12810",0.73872817,{"description":3035,"labels":3036,"number":3037,"owner":3019,"repository":3020,"state":3021,"title":3038,"updated_at":3039,"url":3040,"score":3041},"**Is your feature request related to a problem? Please describe.**\nYes. Currently, when a user encounters a validation error while prescribing medicine, the error messages are either too generic or unclear. This makes it difficult for users to identify what exactly went wrong and how to correct it, leading to frustration and potential workflow delays.\n\n**Describe the solution you'd like**\nWe would like to see specific, descriptive validation error messages that clearly indicate the nature of the issue when prescribing medication\n\n\n\n**Additional context**\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",[],12661,"Clearly Define Validation Errors When Prescribing Medicine","2025-06-19T13:54:30Z","https://github.com/ohcnetwork/care_fe/issues/12661",0.7425928,{"description":3043,"labels":3044,"number":3045,"owner":3019,"repository":3020,"state":3021,"title":3046,"updated_at":3047,"url":3048,"score":3049},"**Describe the bug**\nWhen an exception is added, the slot info text includes unexpected characters, making it unclear.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'My Schedules' \n2. Click on a date with an exception added\n3. See error\n\n**Expected behavior**\nThe message should clearly show intended and actual slots.\n\n**Screenshots**\n\n\u003Cimg width=\"1909\" height=\"888\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/270f210f-3d26-48e5-bcfb-15d0d1878af3\" />\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",[],13092,"Incorrect text shown for `session_slots_info_striked`","2025-07-25T16:59:14Z","https://github.com/ohcnetwork/care_fe/issues/13092",0.7510007,{"description":3051,"labels":3052,"number":3053,"owner":3019,"repository":3020,"state":3054,"title":3055,"updated_at":3056,"url":3057,"score":3058},"**Describe the bug**\nWhen using number input fields (`type=\"number\"`), users can enter the scientific notation character 'e' (or 'E'), which is not desired behavior for fields like dates, pincodes, and age inputs.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any form\n2. Click on number only input\n3. Type 'e'\n4. See error\n\n**Expected behavior**\n- Number input fields should only accept digits (0-9)\n- Scientific notation characters ('e', 'E') should be prevented\n- This is especially important for fields like dates, pincodes, and age where scientific notation is not meaningful\n\n**Screenshots**\n\n\n\n**Desktop (please complete the following information):**\n\n- OS: Fedora\n- Browser: Brave\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",[],12545,"closed","Bug: Scientific notation 'e' character can be entered in number input fields","2025-06-09T10:16:08Z","https://github.com/ohcnetwork/care_fe/issues/12545",0.66510975,{"description":3060,"labels":3061,"number":3062,"owner":3019,"repository":3020,"state":3054,"title":3063,"updated_at":3064,"url":3065,"score":3066},"**Describe the bug**\nVitals fields like respiratory rate, Pulse, Temperature, and blood pressure are taking a few characters as input along with an integer.\n----------SS----------------\n\n\n\nNot able to submit the form with a character as an input in these fields, but even after correcting that particular field, the \"Submit \" button is not available until we refresh the page, which will clear all the other entered data from the form.\n\n----------SS--------\n\n\n\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [https://care.coronasafe.in/facility/d95bf507-055d-403f-acd3-3d331c735140/patient/043edc74-22b9-4efe-b8d7-2695eacb6917/encounter/131ed06a-abbc-4ed9-b9df-ca594e58148c/questionnaire/icuconsultation](url)\n2. Use Credentials: Username: jamesnurse\n Password: James@123\n3. Scroll down to 'Vitals.'\n4. Give input character \"e\" in any fields from vitals.\n5. Add other mandatory fields and submit.\n6. See the error by scrolling to the bottom of the page.\n7. Correct these Vitals fields with integers only and submit again.\n8. \"Submit\" button wont work until the page is refreshed. \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",[],12775,"Vitals fields from ICU Consultation form is taking String as a input of instead of Integer only","2025-07-02T10:23:06Z","https://github.com/ohcnetwork/care_fe/issues/12775",0.6878517,{"description":3068,"labels":3069,"number":3070,"owner":3019,"repository":3020,"state":3054,"title":3071,"updated_at":3072,"url":3073,"score":3074},"**Describe the bug**\nWhen a questionnaire is imported using a valid JSON file, the form fields appear to be populated correctly. However, upon clicking \"Save,\" the system displays validation errors in questions field even tho value is there, and the questionnaire cannot be saved. \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Click on \"Create Questionnaire\"\n2. Click on \"Import from URL\"\n3. Enter a raw JSON URL file, import and try to save it\n4. See error\n\n**Expected behavior**\nShould be able to save a successfully imported JSON.\n\n**Screenshots**\n\u003Cimg width=\"1447\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a57de29c-ae33-43bb-8e70-fb4dcd02416a\" />\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",[],12438,"Unable to Save Questionnaire After Importing from JSON File","2025-05-30T08:11:15Z","https://github.com/ohcnetwork/care_fe/issues/12438",0.7089909,{"description":3076,"labels":3077,"number":3078,"owner":3019,"repository":3020,"state":3054,"title":3079,"updated_at":3080,"url":3081,"score":3082},"**Describe the bug**\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Create a questionnaire with type \"choice\" and option as ValueSet (select a ValueSet that isn't listed on the first page).\n2. Edit the Questionnaire\n3. See error\n\n**Expected behavior**\nThe Valuset should be visible while editing\n\n**Screenshots**\n\n\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",[],12625,"Valueset Missing from Search Field During Edit Questionnaire","2025-06-16T13:39:51Z","https://github.com/ohcnetwork/care_fe/issues/12625",0.7243977,{"description":3084,"labels":3085,"number":3086,"owner":3019,"repository":3020,"state":3054,"title":3087,"updated_at":3088,"url":3089,"score":3090},"**Describe the bug**\nOn the Encounter page, when the user clicks on \"Add Questionnaire\", the system incorrectly displays questionnaires with subject_type = \"patient\" along with those having subject_type = \"encounter\". \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Create a new questionnaire with subject_type = \"patient\".\n2. Go to a patient's Encounter page. \n3. Click on \"Add Questionnaire\".\n4. Observe that the newly created patient-type questionnaire is visible, which is incorrect.\n\n**Expected behavior**\nOnly questionnaires with subject_type = \"encounter\" should be visible when accessed from the Encounter page..\n\n**Screenshots**\n\n\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",[],12782,"Bug: \"Add Questionnaire\" on Encounter Page shows Patient-type Questionnaires","2025-07-14T06:24:48Z","https://github.com/ohcnetwork/care_fe/issues/12782",0.7293955,{"description":3092,"labels":3093,"number":3106,"owner":3019,"repository":3020,"state":3054,"title":3107,"updated_at":3108,"url":3109,"score":3110},"\nMedication Statement, Allergy, Symptom, Diagnosis records with entered-in-error status need not be disabled during edit\n\n\n\n**Describe the bug**\nA clear and concise description of what the bug is.\n\n**To Reproduce**\nSteps to reproduce the behavior:\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",[3094,3097,3100,3103],{"name":3095,"color":3096},"good first issue","7057ff",{"name":3098,"color":3099},"question","d876e3",{"name":3101,"color":3102},"stale","688388",{"name":3104,"color":3105},"needs-triage","ededed",11966,"Structured records uneditable when in entered-in-error status","2025-06-23T16:50:34Z","https://github.com/ohcnetwork/care_fe/issues/11966",0.7304681,["Reactive",3112],{},["Set"],["ShallowReactive",3115],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbt9i1xD-bB4FDpnFqBlX9KNDdOAkGAG92CfgHv19vmc":-1},"/ohcnetwork/care_fe/12970"]