\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,"closed","Validation issue in the charge item definition update page","2025-09-18T18:09:45Z","https://github.com/ohcnetwork/care_fe/issues/13763",0.6287018,{"description":3211,"labels":3212,"number":3213,"owner":3178,"repository":3179,"state":3205,"title":3214,"updated_at":3215,"url":3216,"score":3217},"### Description:\nThe `derived_from_url` field is intended to be optional in some forms. However, once a value is typed and then cleared, form submission is blocked. This happens because Zod validation treats the empty string (\"\") as an invalid URL instead of allowing it as optional\n\n### Screen recording\n\nhttps://github.com/user-attachments/assets/c71a0f97-8a6b-4ee7-b448-abba61a4dda1\n\n### Expected behavior:\n- If the user clears the derived_from_url field, the form should treat it as null/undefined and allow submission.\n- Validation should only enforce proper URL format when a non-empty value is provided.\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",[],13635,"Optional URL field blocks submission when cleared","2025-09-06T14:15:42Z","https://github.com/ohcnetwork/care_fe/issues/13635",0.63578767,{"description":3219,"labels":3220,"number":3221,"owner":3178,"repository":3179,"state":3205,"title":3222,"updated_at":3223,"url":3224,"score":3225},"**Describe the bug**\nWhen we are creating Charge Item Definitions , we are able to leave the Additional Details section empty. But when we are editing the same form , we are receiving error in that section.\n\nhttps://github.com/user-attachments/assets/fa1b028b-9e4e-4783-b175-111bd56f3b80\n\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",[],13307,"Bug: Additional Details Section in Charge Item Definition Edit Form requires validation for null values","2025-08-11T17:36:06Z","https://github.com/ohcnetwork/care_fe/issues/13307",0.64583844,{"description":3227,"labels":3228,"number":3231,"owner":3178,"repository":3179,"state":3205,"title":3232,"updated_at":3233,"url":3234,"score":3235},"\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",[3229,3230],{"name":3172,"color":3173},{"name":3175,"color":3176},13215,"Bug: Validation error on Discounts and Taxes fields in ChargeItemDefinitions","2025-08-04T07:49:13Z","https://github.com/ohcnetwork/care_fe/issues/13215",0.659381,{"description":3237,"labels":3238,"number":3241,"owner":3178,"repository":3179,"state":3205,"title":3242,"updated_at":3243,"url":3244,"score":3245},"**Describe the bug**\nIn the Specimen Definition edit form, removing data from Derived URL optional field is not working\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**\n\nhttps://github.com/user-attachments/assets/46d3245d-4edb-42d3-8f01-9d6020f7393e\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",[3239,3240],{"name":3172,"color":3173},{"name":3175,"color":3176},13266,"Cannot Remove Data from Optional Fields in Specimen Definition Edit Form","2025-08-08T06:48:51Z","https://github.com/ohcnetwork/care_fe/issues/13266",0.66480595,{"description":3247,"labels":3248,"number":3249,"owner":3178,"repository":3179,"state":3205,"title":3250,"updated_at":3251,"url":3252,"score":3253},"**Describe the bug**\nThere is only a toast error when the slug is invalid in charge item definition form. moreover, the autofill slug function generates slug beyond len 25\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Charge Item definition'\n2. Click on 'Add item'\n3. Scroll down to 'slug'\n4. See error\n\n**Expected behavior**\nThere should be valid error shown not only in toast but at the slug field. Also the autofill slug function should only generate slug up to len 25\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/902ca894-0970-4425-949f-c303ce641c4c\n\n**Desktop (please complete the following information):**\n\n- OS: Win 10\n- Browser Opera\n- Version latest\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",[],13745,"No error when slug is invalid in charge item definition form","2025-09-30T09:03:03Z","https://github.com/ohcnetwork/care_fe/issues/13745",0.6865292,{"description":3255,"labels":3256,"number":3260,"owner":3178,"repository":3179,"state":3205,"title":3261,"updated_at":3262,"url":3263,"score":3264},"**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",[3257],{"name":3258,"color":3259},"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.705928,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fF2D4Yp2_nqC1C1QLxyM7z3mK9To2PQXPXA3Vl7T_vyM":-1},"/ohcnetwork/care_fe/13261"]