\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**\nThe issue is caused in FormField → Input usage:\n\n\u003CInput\n type=\"number\"\n min={1}\n defaultValue={1} // ❌ conflict\n {...field} // includes value + onChange\n/>\n\nThis passes both value and defaultValue, leading to the React error.\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",[],13574,"Bug: Input field throws controlled/uncontrolled warning when using auto-fill slot duration toggle","2025-08-31T10:24:24Z","https://github.com/ohcnetwork/care_fe/issues/13574",0.7814841,{"description":3189,"labels":3190,"number":3191,"owner":3173,"repository":3174,"state":3175,"title":3192,"updated_at":3193,"url":3194,"score":3195},"**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to `admin dashboard`\n2. Go to `valueset`\n3. Create valueset with error upfront like no name and no slug \n4. See error\n\n**Expected behavior**\ntriggers form error when user tries to see the preview if error exists and if there is no error then preview sheet should open as usual \n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/e935a74c-73a3-4584-916a-8da6f85cc317\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",[],12884,"Restrict ValueSet preview trigger when there is error in form","2025-07-12T14:19:12Z","https://github.com/ohcnetwork/care_fe/issues/12884",0.79601985,{"description":3197,"labels":3198,"number":3205,"owner":3173,"repository":3174,"state":3206,"title":3207,"updated_at":3208,"url":3209,"score":3210},"**Describe the bug**\nObserved in Resource form where AutoComplete is used for Facility select, the autocomplete is not getting scroll to and focus (like red border) on validation error or any error thrown\n\n\n**Expected behaviour**\nAutoComplete should get focus on error like have red-border just like Select component got red-border in video shared and scroll\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/d5fcf2cd-69a6-4b23-94d0-fcf0362872f7\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",[3199,3202],{"name":3200,"color":3201},"question","d876e3",{"name":3203,"color":3204},"needs-triage","ededed",12672,"closed","`AutoComplete` not getting scroll and focused on error","2025-06-26T13:06:50Z","https://github.com/ohcnetwork/care_fe/issues/12672",0.7447911,{"description":3212,"labels":3213,"number":3216,"owner":3173,"repository":3174,"state":3206,"title":3217,"updated_at":3218,"url":3219,"score":3220},"**Describe the bug**\n\nWhen we submit the form, and there is a error in the schedule create form / edit form, it is not auto scrolling to the error message, so users need to manually check for error\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to profile and create a schedule with past date\n2. submit the form\n3. See error\n\n**Expected behavior**\n\nAuto-scroll to the error message in the schedule create / edit form\n\n**Screenshots**\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",[3214,3215],{"name":3200,"color":3201},{"name":3203,"color":3204},12149,"Add auto-scroll to error fields in schedule creation / edit form","2025-07-22T07:37:10Z","https://github.com/ohcnetwork/care_fe/issues/12149",0.776261,{"description":3222,"labels":3223,"number":3230,"owner":3173,"repository":3174,"state":3206,"title":3231,"updated_at":3232,"url":3233,"score":3234},"The white variant button should be the default design since it blends better with the overall form styling. We can pass a prop to switch to the green variant for ValueSetSelect. While reviewing the code, I noticed we’re duplicating the \u003CSheet> component just to apply different button styles — this could be simplified by using a ternary operator on a single SheetTrigger instead\n\n\n\n\u003Cimg width=\"880\" height=\"813\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/79bf3b6d-a09a-47c5-85a9-f809d5d4cb09\" />\n\ncc: @yash-learner ",[3224,3227],{"name":3225,"color":3226},"stale","688388",{"name":3228,"color":3229},"Development/Refactor","6c7672",13118,"Refactor: Use white button as default for ValueSetSelect and remove duplicate Sheet code","2025-09-29T13:21:59Z","https://github.com/ohcnetwork/care_fe/issues/13118",0.78508765,{"description":3236,"labels":3237,"number":3241,"owner":3173,"repository":3174,"state":3206,"title":3242,"updated_at":3243,"url":3244,"score":3245},"**Describe the bug**\nNo input fields in Create Discount form have required indicator.\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**\nAdd aria-required=\"true\" to Name and Code and correct the \"Field required\" translation\n\n**Screenshots**\n\n\u003Cimg width=\"1911\" height=\"953\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7f170d78-5e8f-494c-9f31-f3632cf83753\" />\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",[3238],{"name":3239,"color":3240},"good first issue","7057ff",13203,"Required indicator (*) missing for fields in AddRequired indicator (*) missing for fields in Create Discount Code form","2025-08-01T17:27:17Z","https://github.com/ohcnetwork/care_fe/issues/13203",0.78609985,{"description":3247,"labels":3248,"number":3249,"owner":3173,"repository":3174,"state":3206,"title":3250,"updated_at":3251,"url":3252,"score":3253},"**Describe the bug**\n\n- When the form is opened, a vertical scrollbar appears even though the content fits within the modal/view area. This affects the UX by giving a false sense of overflowing content.\n- There is minimal vertical spacing between the form labels and their corresponding text fields, making the UI feel cramped and less readable.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Admin Dashboard'\n2. Click on 'RBAC'\n3. Click on 'Add Role'\n4. See error\n\n**Expected behavior**\n\n- Remove the unwanted scroll of the form.\n- Add spacing below labels\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/02f2d9b4-f944-4cd7-8dd3-d66c363b17d6\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",[],12994,"Ui Fix : Remove unnecessary outer scroll from the Add/Edit Role Form in RBAC","2025-07-23T13:14:06Z","https://github.com/ohcnetwork/care_fe/issues/12994",0.7871512,{"description":3255,"labels":3256,"number":3262,"owner":3173,"repository":3174,"state":3206,"title":3263,"updated_at":3264,"url":3265,"score":3266},"Handle back propagation properly with select and selectcontent open inside the EntitySelectionSheet \n\nps: This issue also be present across multiple places in the codebase where we are using select inside the sheet.",[3257,3260,3261],{"name":3258,"color":3259},"enhancement","a2eeef",{"name":3200,"color":3201},{"name":3203,"color":3204},12222,"Handle back propagation with select inside the EntitySelectionSheet","2025-08-21T07:54:41Z","https://github.com/ohcnetwork/care_fe/issues/12222",0.7871638,{"description":3268,"labels":3269,"number":3272,"owner":3173,"repository":3174,"state":3206,"title":3273,"updated_at":3274,"url":3275,"score":3276},"**Describe the bug**\n\nWhen we create the questionnaire, and there is a error in the questionnaire create form / edit form, it is not auto scrolling to the error message, so users need to manually check for error\n\n**Steps to reproduce the behavior:**\n\nGo to questionnaire editor. create a questionnaire\nsubmit the form\nSee error\n\nhttps://github.com/user-attachments/assets/6e86d290-39cb-4e5a-ab33-a2053378d095\n\n",[3270,3271],{"name":3200,"color":3201},{"name":3203,"color":3204},12677,"Add auto-scroll to error fields in Questionnaire Editor","2025-07-01T06:01:37Z","https://github.com/ohcnetwork/care_fe/issues/12677",0.79453635,["Reactive",3278],{},["Set"],["ShallowReactive",3281],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3RNu2A5lcDZ2B0yAVgn_PgVmz2xXyHJLcRnNPw4gIlw":-1},"/ohcnetwork/care_fe/13199"]