\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",[],13763,"Validation issue in the charge item definition update page","2025-09-18T18:09:45Z","https://github.com/ohcnetwork/care_fe/issues/13763",0.6988042,{"description":3227,"labels":3228,"number":3232,"owner":3172,"repository":3173,"state":3213,"title":3233,"updated_at":3234,"url":3235,"score":3236},"**Describe the bug**\nWhen we are entering values in pricing components, it is expecting string values as input but it should be number.\n\nhttps://github.com/user-attachments/assets/c3fb6dfd-e92a-4f59-972f-925fab32ad35\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**\nWe should add zod validation so that pricing component receive numbers as an input.\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",[3229],{"name":3230,"color":3231},"P2","173FC5",13148,"Bug: Add correct zod validation for pricing components in create charge item definition sheet","2025-08-22T07:15:35Z","https://github.com/ohcnetwork/care_fe/issues/13148",0.6994405,{"description":3238,"labels":3239,"number":3243,"owner":3172,"repository":3173,"state":3213,"title":3244,"updated_at":3245,"url":3246,"score":3247},"**Describe the bug**\n\n**1. Raw translation keys showing instead of translated text**\n- Form displays raw translation keys like \"**field_required**\" instead of actual translated messages in both `DiscountCodeForm.tsx` and `DiscountMonetaryComponentForm.tsx`\n\n**2. Validation messages not appearing for factor/amount fields in `DiscountMonetaryComponentForm.tsx`**\n- When factor or amount fields are left empty, no validation error message is displayed even though error message exist.\n- Only the name field shows validation errors, factor/amount fields show no feedback \n\n**3. HTML5 default validation messages**\n- We can use our custom validation message instead of HTML5 default validation messages for better Localization & Internationalization\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Billings\n2. Click on Discount Codes and Discount Components\n3. Leave all the field and submit\n4. See error\n\n**Expected behavior**\n- Form should display proper translated messages like \"This field is required\" instead of raw keys like \"field_required\"\n- When factor or amount fields are empty, validation error message \"Either factor or amount must be provided\" should appear below the respective field\n- Custom validation messages should display instead of browser default messages\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/82d2293b-2bc5-490f-8f76-b17de2bfa490\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",[3240],{"name":3241,"color":3242},"stale","688388",13234,"Validation errors not appearing and translation issues in discount forms","2025-09-02T06:41:08Z","https://github.com/ohcnetwork/care_fe/issues/13234",0.71272695,{"description":3249,"labels":3250,"number":3251,"owner":3172,"repository":3173,"state":3213,"title":3252,"updated_at":3253,"url":3254,"score":3255},"**Describe the bug**\nThe title and status is breaking in activity definition card\n\n\u003Cimg width=\"421\" height=\"438\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/31ab893c-86fe-4e4b-b45e-a0ae1aad2984\" />\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any facility\n2. Click on settings\n3. Select activity definition\n4. Check on mobile view\n5. 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",[],13690,"Improve UI for activity definition card","2025-09-17T11:56:52Z","https://github.com/ohcnetwork/care_fe/issues/13690",0.7145326,{"description":3257,"labels":3258,"number":3259,"owner":3172,"repository":3173,"state":3213,"title":3260,"updated_at":3261,"url":3262,"score":3263},"**Describe the bug**\nIn the **Create Schedule Template form**, when the form is submitted with empty values, most fields correctly show user-friendly validation errors such as `\"This field is required\"`.\nHowever, the fields `Slot Duration` and `Patients per Slot` display raw validation errors:\n- `\"Expected number, received null\"` when left empty.\n- `\"Expected number, received nan\"` when input is typed and then cleared.\n\nThis results in a confusing and inconsistent user experience, especially for non-technical users\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Create Schedule Template page.\n2. Leave all fields empty and click **Save**.\n3. Observe the validation messages for all required fields.\n4. See error\n\n**Expected behavior**\nAll fields should show consistent and user-friendly validation messages:\n- If empty: `This field is required`\n- If invalid: `Please enter a valid number`\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/44622cee-2151-480f-aba6-2c2216c2b81e\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",[],13304,"Inconsistent and Technical Validation Errors in “Create Schedule Template” Form","2025-08-11T17:34:26Z","https://github.com/ohcnetwork/care_fe/issues/13304",0.71927184,["Reactive",3265],{},["Set"],["ShallowReactive",3268],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fhVC4kwtNUDfp526bFNPBNZRk3e_Cc9TeQlD1f3_RILA":-1},"/ohcnetwork/care_fe/14039"]