\n\u003Cimg width=\"1169\" height=\"813\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0f7c103c-c2d4-43e7-933b-6ecbad6d1622\" />\n\n\n\n### Describe\n\nRefer to above screenshots, see there is no any information present regarding Account and Patient for both detail page and print receipt \n\n### steps to Reproduce:\n- Go to any facility \n- Go to billing tab\n- Go to any payment view detail \n- see the error \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",[],13256,"Bug: No Information regarding Account and Patient on Payment detail page and Print","2025-08-04T20:18:38Z","https://github.com/ohcnetwork/care_fe/issues/13256",0.7563617,{"description":3194,"labels":3195,"number":3196,"owner":3178,"repository":3179,"state":3180,"title":3197,"updated_at":3198,"url":3199,"score":3200},"### Describe \nRefer to the screenshot attached, \n- The required field validations for `Slot duration` and `Patient per slot` are not showing any error messages, even when the fields are left empty.\n- The `Number of slots` field shows a confusing error: \"Expected number, received NaN\"\n\n\n\u003Cimg width=\"509\" height=\"816\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a509caa6-2ebc-4135-a331-8790b2bb6181\" />\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",[],13305,"Validation Errors Not Displayed as Expected for Schedule Edit Form ","2025-08-10T18:45:31Z","https://github.com/ohcnetwork/care_fe/issues/13305",0.7602773,{"description":3202,"labels":3203,"number":3206,"owner":3178,"repository":3179,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"\n**Describe the bug**\nWhen a discount or tax is added in the ChargeItemDefinition form, a validation error (Expected string, received null)appears on the corresponding input field.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings'\n2. Click on 'ChargeItemDefinitions'\n3. Click on 'Add Definition'\n4. Click on 'Add discount' or 'Add tax' dropdown.\n5. See error\n\n**Expected behavior**\nWhen a discount or tax is added, the input should accept the default value without showing a validation error.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/2aec7375-9430-4924-96f0-8d105b910066\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",[3204,3205],{"name":3172,"color":3173},{"name":3175,"color":3176},13215,"closed","Bug: Validation error on Discounts and Taxes fields in ChargeItemDefinitions","2025-08-04T07:49:13Z","https://github.com/ohcnetwork/care_fe/issues/13215",0.697344,{"description":3213,"labels":3214,"number":3218,"owner":3178,"repository":3179,"state":3207,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**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",[3215],{"name":3216,"color":3217},"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.71775186,{"description":3224,"labels":3225,"number":3229,"owner":3178,"repository":3179,"state":3207,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**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",[3226],{"name":3227,"color":3228},"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.7329801,{"description":3235,"labels":3236,"number":3237,"owner":3178,"repository":3179,"state":3207,"title":3238,"updated_at":3239,"url":3240,"score":3241},"https://github.com/user-attachments/assets/cd5cfe15-bd9a-4902-8c73-5b838fa0908a\n\n\nhttps://github.com/user-attachments/assets/21ec7d18-a3de-4ee8-8b7e-80fd4ea862f3\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\n",[],13366,"Clear error message for slug when auto filled for Charge item and Tag Config form","2025-08-19T10:13:36Z","https://github.com/ohcnetwork/care_fe/issues/13366",0.7340577,{"description":3243,"labels":3244,"number":3245,"owner":3178,"repository":3179,"state":3207,"title":3246,"updated_at":3247,"url":3248,"score":3249},"**Describe the bug**\nWhen selecting the checkbox for an emergency number, validation error is displayed.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Patient Registration.'\n2. Click on check box of same as emergency number.\n3. . See error , validation error is showing.\n\nhttps://github.com/user-attachments/assets/c247ff3d-10a8-4443-add5-f9b3df2b5d65\n\n**Expected behavior**\nNo validation error should be triggered when the checkbox is selected\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",[],13490,"Incorrect Error Message on Emergency Contact Field","2025-08-25T14:40:26Z","https://github.com/ohcnetwork/care_fe/issues/13490",0.73616767,{"description":3251,"labels":3252,"number":3253,"owner":3178,"repository":3179,"state":3207,"title":3254,"updated_at":3255,"url":3256,"score":3257},"**Describe the bug**\n\nWhen we are trying to update the charge item definition , and the description, derived url and purpose are left blank, the validation is been throwing error and not allowing users to update it\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Login to the page\n2. Click on charge item and open up any existing CI\n3. try to update them\n4. See error\n\n**Expected behavior**\n\nthe validation shouldn't been thrown for optional field in the CI, if they are left blank\n\n**Screenshots**\n\n\u003Cimg width=\"1843\" height=\"757\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d57d25b0-b0b7-4b29-8d82-8a515209b332\" />\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.7381701,{"description":3259,"labels":3260,"number":3263,"owner":3178,"repository":3179,"state":3207,"title":3264,"updated_at":3265,"url":3266,"score":3267},"**Describe the bug**\nIn the Charge Definition Form, the `derived_from_uri` field is optional. However, if a user accidently focuses the field or leaves it empty (after typing and clearing), the form throws a \"Invalid URL\" error on submit.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Charge Item Definitions'\n2. Click on 'Add Definition' or 'Edit' button\n3. Click on 'Derived from URI' field and leave it empty\n4. Attempt to submit the form\n5. See error\n\n**Expected behavior**\nThe form should allow submission if the field is empty, regardless of whether it was focused or modified.\n\n**Screenshots**\n\n\u003Cimg width=\"1898\" height=\"905\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3bc6abac-1214-4f86-a958-0fb372c236b0\" />\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",[3261,3262],{"name":3172,"color":3173},{"name":3175,"color":3176},13261,"Optional `derived_from_uri` field triggers validation error","2025-08-06T05:56:29Z","https://github.com/ohcnetwork/care_fe/issues/13261",0.74247104,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fW6pPBj3IBi9D3flGahcF9VzVeXJXHAHA8eK_zJzeuRw":-1},"/ohcnetwork/care_fe/13618"]