\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",[],12886,"Fix console warning for Encounter view page","2025-07-14T15:07:11Z","https://github.com/ohcnetwork/care_fe/issues/12886",0.67808986,{"description":3208,"labels":3209,"number":3216,"owner":3172,"repository":3173,"state":3194,"title":3217,"updated_at":3218,"url":3219,"score":3220},"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",[3210,3213],{"name":3211,"color":3212},"question","d876e3",{"name":3214,"color":3215},"needs-triage","ededed",13257,"Mismatch between results in Pages for Permission page","2025-08-06T13:00:43Z","https://github.com/ohcnetwork/care_fe/issues/13257",0.69429547,{"description":3222,"labels":3223,"number":3224,"owner":3172,"repository":3173,"state":3194,"title":3225,"updated_at":3226,"url":3227,"score":3228},"**Describe the bug**\nCurrently the latest comments in the Resource request page are getting pushed at last this should not happen because users have to navigate in order to see the latest comments.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Resource request\n2. Click on a resource\n3. Scroll down to the comments and type a comment\n4. See error\n\n**Expected behavior**\nThe latest comments should be visible at the top\n\n**Screenshots**\n\n\u003Cimg width=\"1861\" height=\"835\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c2341439-d440-46e2-a8be-a1458e4f4963\" />\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",[],12798,"Resource Request details latest comments are getting pushed at the last","2025-07-06T09:04:49Z","https://github.com/ohcnetwork/care_fe/issues/12798",0.69429636,{"description":3230,"labels":3231,"number":3234,"owner":3172,"repository":3173,"state":3194,"title":3235,"updated_at":3236,"url":3237,"score":3238},"**Screenshots**\n\nhttps://github.com/user-attachments/assets/5d7baa2c-d410-427b-8b18-c51c84d1c3a1\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",[3232,3233],{"name":3211,"color":3212},{"name":3214,"color":3215},12655,"Unable to Submit Consent Edit Form","2025-06-23T12:19:35Z","https://github.com/ohcnetwork/care_fe/issues/12655",0.6955687,{"description":3240,"labels":3241,"number":3242,"owner":3172,"repository":3173,"state":3194,"title":3243,"updated_at":3244,"url":3245,"score":3246},"**Expected behavior**\nDisable submit button when no changes are made\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/dd2f8423-bdc6-4c22-aee0-9498be61b3bd\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",[],12449,"Bug: FacilityOrg form is submittimg even when no changes are made in Edit","2025-05-29T10:09:57Z","https://github.com/ohcnetwork/care_fe/issues/12449",0.6990316,{"description":3248,"labels":3249,"number":3253,"owner":3172,"repository":3173,"state":3194,"title":3254,"updated_at":3255,"url":3256,"score":3257},"**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to `admin dashboard`\n2. Go to `valueset`\n3. Create valueset with error upfront like no name and no slug \n4. See error\n\n**Expected behavior**\ntriggers form error when user tries to see the preview if error exists and if there is no error then preview sheet should open as usual \n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/e935a74c-73a3-4584-916a-8da6f85cc317\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",[3250,3251,3252],{"name":3211,"color":3212},{"name":3191,"color":3192},{"name":3214,"color":3215},12884,"Restrict ValueSet preview trigger when there is error in form","2025-10-10T08:06:48Z","https://github.com/ohcnetwork/care_fe/issues/12884",0.7021745,{"description":3259,"labels":3260,"number":3261,"owner":3172,"repository":3173,"state":3194,"title":3262,"updated_at":3263,"url":3264,"score":3265},"**Describe the bug**\nPrevent the creation of a Bed location unless a valid parent location is already selected. This ensures proper hierarchical structure and avoids orphaned Bed entries in the system.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to `Location` tab under setting nav\n2. Add on `Add Location` without selecting any parent location\n3. Create a bed type location\n4. See error \n\n**Expected behaviour**\nRemove the Bed form from form options when no parent is present\n\n> [!NOTE]\n> Expected behaviour could be different , this issue needs a review from core members\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/0bc62535-0af0-4bd3-97a0-4342e2566611\n\n\n> [!TIP]\n> GOOD FIRST ISSUE depends on expected behaviour decided 👍 \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",[],12664,"Restricting Creating Bed Location when no parent location is present","2025-06-19T19:11:09Z","https://github.com/ohcnetwork/care_fe/issues/12664",0.7027404,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fY0y_gjrBWU4g-Uo4re0p1yMH1qM8A-Zf5a4lHAIAmaA":-1},"/ohcnetwork/care_fe/11641"]