component inline without changing the URL. This can be confusing to the user because the URL still shows the protected route, but the content displayed is the login form.\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",[3030,3033],{"name":3031,"color":3032},"question","d876e3",{"name":3034,"color":3035},"needs-triage","ededed",12669,"closed","Redirect unauthenticated users to /login instead of rendering Login component in-place","2025-06-27T03:25:39Z","https://github.com/ohcnetwork/care_fe/issues/12669",0.6757202,{"description":3043,"labels":3044,"number":3048,"owner":3020,"repository":3021,"state":3037,"title":3049,"updated_at":3050,"url":3051,"score":3052},"### Description\n\nNon-superuser users are able to access **admin-only routes** (like `admin/questionnaire`) by **typing the URL directly into the browser**. This bypasses intended access restrictions.\n\n\n\n### Expected Behaviour\n\nNon-superusers should be **blocked or redirected** from admin routes with an appropriate error page as shown in video\n\n\n### Bug Video\n\nhttps://github.com/user-attachments/assets/3ee57de9-921a-4cc5-b352-9ec4517a93b3\n\n### Expected Behavior Video\n\n\nhttps://github.com/user-attachments/assets/2a8849fa-12b6-4506-9291-171320f1d0e5\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\n",[3045],{"name":3046,"color":3047},"stale","688388",12591,"Restrict the access to admin Routes to admin only","2025-07-30T15:15:47Z","https://github.com/ohcnetwork/care_fe/issues/12591",0.72616774,{"description":3054,"labels":3055,"number":3058,"owner":3020,"repository":3021,"state":3037,"title":3059,"updated_at":3060,"url":3061,"score":3062},"**Describe the bug**\nOn verify patient page, it is making twice backend request for same api and update to use \u003CLoading /> instead of skeleton for the same page \n\nCheckout video for steps to reproduce \n\nhttps://github.com/user-attachments/assets/10c6f24a-f009-4869-add3-57ccff74f649\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",[3056,3057],{"name":3031,"color":3032},{"name":3034,"color":3035},13010,"Bug: Double backend request for Verify Patient Page","2025-07-21T16:32:26Z","https://github.com/ohcnetwork/care_fe/issues/13010",0.74740434,{"description":3064,"labels":3065,"number":3066,"owner":3020,"repository":3021,"state":3037,"title":3067,"updated_at":3068,"url":3069,"score":3070},"**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.75319266,{"description":3072,"labels":3073,"number":3076,"owner":3020,"repository":3021,"state":3037,"title":3077,"updated_at":3078,"url":3079,"score":3080},"**Describe the bug**\nPatient Encounter Consent Records/Files do not change to read-only after `entered-in-error`. \nCurrently, we can change an entered-in-error consent record/file back to any other state (e.g active). \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any patient encounter\n2. Click on consents tab\n3. Create a consent record as active\n4. Switch to entered_in_error status\n5. Switch again to any other state\n7. See error\n\n **Expected behavior**\nOnce, user sets it as entered-in-error, it should be disabled and become read-only, preventing any further status changes.\n\n**Video Demo**\n\nhttps://github.com/user-attachments/assets/a33fee24-5e62-4f97-8784-2980025ef427\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",[3074,3075],{"name":3031,"color":3032},{"name":3034,"color":3035},12431,"Bug: Patient Encounter Consent records do not change to read-only after `entered-in-error`","2025-05-28T10:12:23Z","https://github.com/ohcnetwork/care_fe/issues/12431",0.7561741,{"description":3082,"labels":3083,"number":3084,"owner":3020,"repository":3021,"state":3037,"title":3085,"updated_at":3086,"url":3087,"score":3088},"**Describe the bug**\nTooltips for the \"Last Logged In\" status appear inconsistently across user cards, causing an uneven experience when hovering over login info.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to user management page in the users section \n2. hover on the last logged in part\n3. see the tooltip inconsistent behavior\n\n\n**Expected behavior**\nTooltips should be consistent for all.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/39711ed8-9778-4c32-a149-d1f7d180212c\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",[],13075,"Bug: Tooltip Inconsistency for Last Login Info in User Management Page","2025-07-25T03:08:14Z","https://github.com/ohcnetwork/care_fe/issues/13075",0.75678587,{"description":3090,"labels":3091,"number":3092,"owner":3020,"repository":3021,"state":3037,"title":3093,"updated_at":3094,"url":3095,"score":3096},"**Describe the bug**\n`batch_requests` errors are not properly handled in the frontend causing page crashes\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings > Locations > Add Location > Create Multiple Beds Locations'\n2. If you don't have permission you'll see page crash\n\n**Screenshots**\n\n\n\n**Desktop (please complete the following information):**\n- Chrome on Windows 11\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",[],11641,"Permission Errors causing Page Crash","2025-07-30T08:18:44Z","https://github.com/ohcnetwork/care_fe/issues/11641",0.7589791,{"description":3098,"labels":3099,"number":3100,"owner":3020,"repository":3021,"state":3037,"title":3101,"updated_at":3102,"url":3103,"score":3104},"**Describe the bug**\nWhen we are going in org (Staff/Doctors) , then we need to do hard refresh to fetch all the data\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/organization/0b769676-a71b-49fc-8187-b8d81101109e)\n2. Click on Staff/Doctors/Administrator\n3. See error\n\n**Expected behavior**\nData should be fetched without hard refresh\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/88693628-3489-4f2f-8ea4-f82e08b1fbcf\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",[],12487,"Bug: Org page required hard refresh to fetch data","2025-06-04T09:02:21Z","https://github.com/ohcnetwork/care_fe/issues/12487",0.7613748,{"description":3106,"labels":3107,"number":3109,"owner":3020,"repository":3021,"state":3037,"title":3110,"updated_at":3111,"url":3112,"score":3113},"**Describe the bug**\nAfter logout, input labels become unclickable and login fails until the page is hard refreshed.\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**\nAfter logout, input labels should remain clickable and login should work without needing a hard refresh.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/17fa0f4d-3b26-43c6-a13c-11451f41c985\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",[3108],{"name":3046,"color":3047},12073,"Cannot Login and Input Label Becomes Unclickable After Logout Until Hard Refresh","2025-07-30T09:27:17Z","https://github.com/ohcnetwork/care_fe/issues/12073",0.7618067,["Reactive",3115],{},["Set"],["ShallowReactive",3118],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fCiDFIIrTMAmA1EuXa-U9470dl0BV66TjPI-ULkc-sxE":-1},"/ohcnetwork/care_fe/12567"]