\n\nhow it should be ⬇️\n\n\u003Cimg width=\"264\" height=\"105\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d049e96b-3f93-4f45-9521-746ea9226d03\" />\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",[],13387,"ohcnetwork","care_fe","open","Responsiveness Issue in Discount Monetary Components Section","2025-08-16T06:58:28Z","https://github.com/ohcnetwork/care_fe/issues/13387",0.6393496,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Description:** There are inconsistent and incorrect validation behaviors in the Create Discount Component form\n\n- Fields like Title accept whitespace as valid input.\n- Fields like discount amount or factor display \"Expected number, received null\" when left empty inconsistent with other required fields that show \"This field is required\".\n\nhttps://github.com/user-attachments/assets/ecda14b9-1a68-4085-b060-c64abb63f826\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Open Create Discount Component.\n- Leave Title empty → Save button enabled.\n- Enter only spaces in these fields → bypasses error message.\n- Leave discount amount field empty → error shows \"Expected number, received null\".\n\n**Expected behavior**\n\n- Whitespace-only input should be treated as empty and trigger \"This field is required\".\n- Numeric fields should also display a user-friendly message like \"This field is required\".",[],14040,"Inconsistent validation behaviors in the Discount Monetary Components","2025-10-12T08:13:37Z","https://github.com/ohcnetwork/care_fe/issues/14040",0.7091041,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Description:**\n\nCurrently, in DiscountCodeForm, the Save button becomes enabled when the user enters just spaces in the name or code fields and it is accepting white space.\n\nhttps://github.com/user-attachments/assets/740e68cd-7499-46e1-85db-f81643ca9f36\n\n**Expected Behavior:**\n\n- Fields should not accept values containing only spaces.\n\n---\n\n🚨 DO NOT EDIT BELOW THIS LINE 🚨\nInstructions for Requesting Assignment:\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\nDescribe 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\nExpected Timeline:\n\nEnd date: [Expected submission date of a completed Pull Request]\nAdditional 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\n",[],14021,"Proper Validation for DiscountCodeForm to Prevent Whitespace-Only Inputs","2025-10-09T17:14:12Z","https://github.com/ohcnetwork/care_fe/issues/14021",0.73339546,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Description**\nThis issue addresses UI inconsistencies in the Patient Tag drop down menu of \"Add Patient Details\" page:\n\n- Tag Menu Dropdown: The height of the search input as well as the menu items need to be adjusted to align with our design system.\n\n- Keyboard Shortcuts: The size of the keyboard shortcuts is inconsistent and needs to be fixed.\n\n- The padding for each tag option within the dropdown should be consistent with the provided Figma file, ensuring proper alignment and spacing.\n\n**Steps to Reproduce**\n\n1. Navigate to Add Patient's details page.\n\n2. Scroll down to the Patient Tags field.\n\n3. Open the dropdown menu.\n\n4. Observe the current option height.\n\n**Expected Behaviour**\n\n- The tag menu dropdown should adhere to the following specifications:\n\n - The search input field at the top of the dropdown should have a fixed height of 40 pixels.\n\n - The padding for each tag option within the dropdown should be consistent with the provided Figma file, ensuring proper alignment and spacing. \n\n- Keyboard Shortcuts\n\n - The size of the keyboard shortcut indicators should match the design specifications. They currently appear smaller than intended. \n\n- Add a secondary button to complete the action.\n\n\n**Visual Reference**\n\n\u003Cimg width=\"752\" height=\"710\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/23009867-03c6-44c4-acd4-4adfbffcb3d4\" />\n\u003Cimg width=\"743\" height=\"705\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7f098772-6e61-4754-a5e5-b94b509b11fb\" />\n\u003Cimg width=\"730\" height=\"636\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/990db087-0e47-4f6d-83b5-b90be8ac1d0a\" />\n\n**Proposed Solution**\nAttached screenshot for reference\n\u003Cimg width=\"1110\" height=\"1210\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/94e1fa1c-2e40-48f9-a230-14043a90198d\" />\nRefer the figma file for the correct dimensions https://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=26304-10329&t=AskluDORl8G3ixs5-1\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",[],13732,"Enhance usability by solving the UI inconsistencies on the \"Add Patient Details\" page","2025-09-17T11:43:03Z","https://github.com/ohcnetwork/care_fe/issues/13732",0.770028,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3174,"title":3207,"updated_at":3208,"url":3209,"score":3210},"**Describe the bug**\nIn the **Register New Patient** form, under the **Deceased Status** section, the check icon inside the “Mark as deceased” checkbox appears **misaligned**, it’s not centered properly within the checkbox. \n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n \n1. Go to the **Register New Patient** form. \n2. Scroll to the **Deceased Status** section. \n3. Check the **“Mark as deceased”** checkbox. \n4. Observe the check icon alignment.\n\n**Expected behavior**\nThe check icon should be **vertically and horizontally centered** within the checkbox, maintaining consistent spacing similar to other checkbox components across the application. \n\n\n**Screenshots**\n\n\u003Cimg width=\"586\" height=\"232\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/567e4247-0327-44b3-8070-39c9f94af21e\" />\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",[],14036,"Misaligned Check Icon in “Mark as Deceased” Checkbox","2025-10-12T07:20:05Z","https://github.com/ohcnetwork/care_fe/issues/14036",0.77125347,{"description":3212,"labels":3213,"number":3214,"owner":3172,"repository":3173,"state":3215,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**Describe the bug**\nIn the Product Knowledge form, the remove button in 'Alternative Names' section is misaligned and the one in 'Product Definition' is styled differently with a label (Remove Definition), unlike others.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Product Knowledge'\n2. Click on 'Edit' or 'Add Product Knowledge' button\n3. Scroll down to see the error\n\n**Expected behavior**\nAll remove buttons should have consistent styling and alignment across the form.\n\n**Screenshots**\n\n\u003Cimg width=\"1896\" height=\"977\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/895d76af-298c-43e0-b563-788f23ae9719\" />\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",[],13270,"closed","Inconsistent styling and alignment of remove buttons in form fields","2025-08-06T06:45:09Z","https://github.com/ohcnetwork/care_fe/issues/13270",0.7391098,{"description":3221,"labels":3222,"number":3223,"owner":3172,"repository":3173,"state":3215,"title":3224,"updated_at":3225,"url":3226,"score":3227},"**Describe the bug**\nThere is overlapping of button component and text in mobile view.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Product Knowledge\n2. Click on Create Product Knowledge\n3. Scroll down to Storage Guidelines\n4. See error\n\n**Expected behavior**\nThe components should be responsive and should not overlap .\n\n**Screenshots**\n\n\u003Cimg width=\"346\" height=\"364\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0b525165-f0a5-409d-95c1-5cbded836f4a\" />\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",[],13386,"Overlapping in Create Product Knowledge Page","2025-08-18T11:30:01Z","https://github.com/ohcnetwork/care_fe/issues/13386",0.7415289,{"description":3229,"labels":3230,"number":3231,"owner":3172,"repository":3173,"state":3215,"title":3232,"updated_at":3233,"url":3234,"score":3235},"**Describe the bug**\nIn the newly created appointments view, the badge text spacing is not even. There is more space in the top compare to the bottom.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Appointments'\n2. See error\n\n**Expected behavior**\nThe y-space should be equal.\n\n**Screenshots**\n\n\u003Cimg width=\"1338\" height=\"406\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/41525077-93c0-48dc-a531-26fd89b29bf1\" />\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",[],13051,"Uneven Vertical Padding in Badge Text on Appointments View","2025-08-13T18:01:02Z","https://github.com/ohcnetwork/care_fe/issues/13051",0.7475687,{"description":3237,"labels":3238,"number":3239,"owner":3172,"repository":3173,"state":3215,"title":3240,"updated_at":3241,"url":3242,"score":3243},"\u003Cimg width=\"918\" height=\"769\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/49fa4d1f-3651-4cd5-ae55-b2c8c127bc50\" />\n\n### Steps to reproduce:\n- Go to any facility\n- In the sidebar, navigate to the Billing tab\n- In the Billing tab, click on the Payment tab\n- In the Payment tab, on any payment and select View Details\n- Click on Print Receipt.\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",[],13236,"Misalignment of Badges in Payment Receipt","2025-08-14T07:15:49Z","https://github.com/ohcnetwork/care_fe/issues/13236",0.75313395,{"description":3245,"labels":3246,"number":3247,"owner":3172,"repository":3173,"state":3215,"title":3248,"updated_at":3249,"url":3250,"score":3251},"**Describe the bug**\nOn the **Product Details** page, the \"Tag\" (Status badge) and \"Edit\" button are misaligned and appear cluttered in both mobile and desktop views. This affects the visual consistency and usability of the UI.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Settings -> Product\n2. Click on See Details on any of the existing Product (if it is not there, add one and then see details)\n3. See error\n\n**Expected behavior**\nThe \"Tag\" and \"Edit\" button should be properly aligned with appropriate spacing, maintaining a clean and organized layout across all screen sizes.\n\n**Screenshots**\n\n\u003Cimg width=\"1150\" height=\"209\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/622dff5a-78cb-4fca-81d5-aab5897f9537\" />\n\n\u003Cimg width=\"264\" height=\"585\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e26174a5-0456-4c66-9065-0f8049ce1dfd\" />\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",[],13284,"Tag and Edit Button Misalignment on Product Page (Mobile and Desktop View)","2025-08-19T11:11:58Z","https://github.com/ohcnetwork/care_fe/issues/13284",0.76159376,["Reactive",3253],{},["Set"],["ShallowReactive",3256],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3O-5lUHtuhMc3tz_uGX5I7NnIpCHyizu9GVNZwobrSc":-1},"/ohcnetwork/care_fe/14041"]