\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Devices\n2. Create a device with long name\n3. 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",[3206],{"name":3207,"color":3208},"stale","688388",13308,"closed","Bug: Device name is overflowing and needs responsiveness","2025-09-03T10:14:01Z","https://github.com/ohcnetwork/care_fe/issues/13308",0.70615065,{"description":3216,"labels":3217,"number":3221,"owner":3172,"repository":3173,"state":3210,"title":3222,"updated_at":3223,"url":3224,"score":3225},"**Describe the bug**\nCurrently, there is inconsistency in how users are rendered across different parts of the app.\nIn some places, we display the username, while in others, we display the user’s full name.\n\n**To Reproduce**\nFile an encounter and update diagnosis, symptom medication and allergies. \n\n\n**Expected behavior**\nRending user's full name across the app wherever Logged By is captured.\n\n**Screenshots**\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",[3218],{"name":3219,"color":3220},"good first issue","7057ff",12118,"Make User Rendering Consistent Across the App","2025-07-23T15:16:41Z","https://github.com/ohcnetwork/care_fe/issues/12118",0.7194575,{"description":3227,"labels":3228,"number":3229,"owner":3172,"repository":3173,"state":3210,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**Describe the bug**\nWhen creating a new ValueSet, if the slug is not unique, the error is only displayed in a popup notification and not under the slug field itself. Show the uniqueness error below the slug field, not just in a popup, for a clearer user experience.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Valueset\n2. Click on Create Valueset\n3. Add already existing valueset's slug\n4. Click on create\n4. See error\n\n**Expected behavior**\nIf the slug is not unique, an error message should appear directly below the slug input field to clearly indicate the problem, in addition to—or instead of—the popup notification.\n\n**Screenshots**\n\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",[],13501,"Improve slug error visibility in ValueSet form","2025-09-03T14:18:59Z","https://github.com/ohcnetwork/care_fe/issues/13501",0.7307623,{"description":3235,"labels":3236,"number":3238,"owner":3172,"repository":3173,"state":3210,"title":3239,"updated_at":3240,"url":3241,"score":3242},"**Describe the bug**\n\nCurrently when user selects the locations , it is not showing in the readable format ( name of the location is not showing after selecting it). Instead it is showing their id in the form while editing.\n\nhttps://github.com/user-attachments/assets/de61b84c-3997-4ded-93d5-87797ad0cfe4\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/facility/b90bf759-077c-46f4-a916-817f332a5a60/settings/healthcare_services/555fce9a-f35b-4766-b9fc-25f760a67989/edit)\n2. Click on Edit form if it not in edit mode\n3. Scroll down to location\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",[3237],{"name":3207,"color":3208},13216,"Use readable names for selected location in Healthcare Services form","2025-09-19T08:09:03Z","https://github.com/ohcnetwork/care_fe/issues/13216",0.73259443,{"description":3244,"labels":3245,"number":3252,"owner":3172,"repository":3173,"state":3210,"title":3253,"updated_at":3254,"url":3255,"score":3256},"**Describe the bug**\nIn mobile view, the config card shows incorrect line breaks and awkward spacing not only for the name, but also for the status badge (\"Inactive\") and the description text. This leads to poor readability and inconsistent UI.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Admin Dashboard\n2. Click on Patient Identifier Config\n3. Scroll down to Card with detials\n4. See error\n\n**Expected behavior**\nThe config card should display the name, status badge, and description in a clear, continuous layout with proper wrapping and spacing, maintaining consistency regardless of screen size.\n\n**Screenshots**\n\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**\nThe ValueSet preview has consistent UI even for small screens, replicaitng it here could solve this issue\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",[3246,3249],{"name":3247,"color":3248},"question","d876e3",{"name":3250,"color":3251},"needs-triage","ededed",13500,"Patient Identifier Config Card Name Breaks Incorrectly in Mobile View","2025-08-25T14:46:52Z","https://github.com/ohcnetwork/care_fe/issues/13500",0.74177635,{"description":3258,"labels":3259,"number":3263,"owner":3172,"repository":3173,"state":3210,"title":3264,"updated_at":3265,"url":3266,"score":3267},"**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",[3260],{"name":3261,"color":3262},"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.7463327,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fowBAC7b3BjmIGIlknvjs_nOnbImtOONvhgsp-LAD-TY":-1},"/ohcnetwork/care_fe/12759"]