\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Login as superadmin/admin\n- Go to Admin Dashboard\n- Go to Organization Tab\n- See the current UI \n\n\n\n**Expected Design**\n >[!TIP]\nRefer to desing for dept/team under any facility and match the exact design like table and card\n\nhttps://github.com/user-attachments/assets/1b63cc23-5d85-4477-b0c0-32776bb811bf\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",[],13042,"Update the design for Goverance, Supplier and Roles under Organization tab","2025-07-28T05:44:38Z","https://github.com/ohcnetwork/care_fe/issues/13042",0.81249106,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"Description\nCurrently, our system disallows duplicate diagnosis and symptom entries entirely. However, this strict check creates unnecessary limitations when the same diagnosis or symptom legitimately appears more than once over time.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Go to any live encounter in facility \n- click on add diagnosis or add symptom \n- See the error for diagnosis and symptom question\n\n\nslack conversation : https://rebuildearth.slack.com/archives/C010GQBMFJ9/p1752585579887739\n\nExpected Behavior: **Wanted it for all three Allergy, diagnosis and symptom**\n- The duplicate check should only apply to unsaved (newly added) items.\n- Once saved, the same allergy, diagnosis or symptom can be added again in the future\n- The main goal is to prevent accidental duplicate entries while adding, not to block valid clinical updates.\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",[],12949,"Allow duplicate Allergy, diagnosis and symptoms if already saved , prevent only during new entry","2025-07-16T06:10:05Z","https://github.com/ohcnetwork/care_fe/issues/12949",0.83313,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"**Describe the bug**\nNew role can be added without giving any permission. \n\n**Expected behavior**\nMaybe an error message showing at least one permission should be selected.\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",[],12866,"closed","RBAC role creation","2025-07-14T08:19:51Z","https://github.com/ohcnetwork/care_fe/issues/12866",0.7922112,{"description":3213,"labels":3214,"number":3224,"owner":3172,"repository":3173,"state":3207,"title":3225,"updated_at":3226,"url":3227,"score":3228},"\nAfter creating a questionnaire, users often realise a question belongs in another section as well. Recreating it in a new group, is error-prone and time-consuming, especially for complex questionnaires. Would be great to have an option to copy/ move questions between groups.\n\nInstance - When we create questionnaire, many subset question might be needed to be used again in multiple places, otherwise we need to rewrite everything. It will be a waste to energy\n",[3215,3218,3221],{"name":3216,"color":3217},"question","d876e3",{"name":3219,"color":3220},"P1","519BFE",{"name":3222,"color":3223},"needs-triage","ededed",12528,"in Questionnaire - Move a Question Between Groups","2025-06-24T10:00:26Z","https://github.com/ohcnetwork/care_fe/issues/12528",0.8036846,{"description":3230,"labels":3231,"number":3234,"owner":3172,"repository":3173,"state":3207,"title":3235,"updated_at":3236,"url":3237,"score":3238},"Currently, when rescheduling an appointment, the reassignment can only be made to the originally assigned user. There is no option to assign it to a different team member during the reschedule process. Requesting the ability to reassign appointments to another team member at the time of rescheduling to improve operational flexibility.\n\n@aravindm4 \n\n\u003Cimg width=\"1543\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b8d80df9-ac76-4145-a462-67c219ff7c24\" />",[3232,3233],{"name":3216,"color":3217},{"name":3222,"color":3223},11987,"Reassigning Rescheduled Appointments","2025-06-15T07:46:53Z","https://github.com/ohcnetwork/care_fe/issues/11987",0.8121802,{"description":3240,"labels":3241,"number":3244,"owner":3172,"repository":3173,"state":3207,"title":3245,"updated_at":3246,"url":3247,"score":3248},"https://github.com/user-attachments/assets/3dc0804a-404d-4627-8fdb-ec5cb4a15a66\n\n### Steps to Reproduce:\n- Login as Super-admin \n- Go to Admin Dashboard \n- In Sidebar, go to Permission tab under RBAC tab\n- see the error (May be you need to create few roles to see the error and have pagination enable)\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",[3242,3243],{"name":3216,"color":3217},{"name":3222,"color":3223},13257,"Mismatch between results in Pages for Permission page","2025-08-06T13:00:43Z","https://github.com/ohcnetwork/care_fe/issues/13257",0.8155942,{"description":3250,"labels":3251,"number":3252,"owner":3172,"repository":3173,"state":3207,"title":3253,"updated_at":3254,"url":3255,"score":3256},"#### Description:\n- The same icons are being used in multiple places within the application, representing different actions or entities. This can cause confusion for users.\n\n#### Affected Areas:\n- Users Tab:\n\"Link\" and \"Add User\" share the same icon.\n- Sidebar:\n\"Search Patient\" and \"Encounters\" have the same icon.\n\"Resource\" and \"Organization\" share the same icon.\n\n\n#### Expected Behavior:\n- Each action or entity should have a distinct and relevant icon to clearly represent its purpose.\n\n#### Proposed Solution:\n- Update the icons for these sections to ensure each one is unique and contextually appropriate.\n- Consult with the design team to select new icons that align with the application's design system and improve user experience.\n- \n#### Steps to Reproduce:\n- Navigate to the Users tab – observe the icons for \"Link\" and \"Add User.\"\n- Open the sidebar – observe the icons for \"Search Patient,\" \"Encounters,\" \"Resource,\" and \"Organization.\", \"Appointments\" and \"Schedules\"\n\n\n\n\n",[],9777,"Duplicate Icons Used in Different Contexts Across Application","2025-06-04T01:28:03Z","https://github.com/ohcnetwork/care_fe/issues/9777",0.82897913,{"description":3258,"labels":3259,"number":3260,"owner":3172,"repository":3173,"state":3207,"title":3261,"updated_at":3262,"url":3263,"score":3264},"**Describe the bug**\nThe search bar in the Roles page does not filter the roles list based on the user’s input. Regardless of the search term entered, the full list of roles remains visible.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Log in as superadmin\n2. Click on RBAC -> Roles\n3. Search Roles and see the error\n\n**Expected behavior**\nTyping in the search bar should dynamically filter and display only the roles that match the entered text\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/9f153f6e-0ec3-4f77-8fc0-4acf54f3ab14\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",[],13083,"Role Search Bar Not Filtering Roles List","2025-07-31T12:45:51Z","https://github.com/ohcnetwork/care_fe/issues/13083",0.831321,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fGJlkBgBZM0qSuKvaXNQpjLW7Hmcto8TC2TGVuwuc9Hg":-1},"/ohcnetwork/care_fe/13809"]