\n\n\u003Cimg width=\"1452\" height=\"899\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f1798fb1-b5bc-47ab-ae9e-dfa55ab9ff2c\" />\n\n**Desktop (please complete the following information):**\n\n- iOS\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",[],13474,"ohcnetwork","care_fe","open","Locations are not displayed in the map even when it is visible in the list","2025-08-22T11:52:02Z","https://github.com/ohcnetwork/care_fe/issues/13474",0.725018,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"Next to Emergency Contact field, need a field to add a another contact point.\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",[],13153,"Option to add Contact Point details in Patient profile page","2025-07-30T08:06:39Z","https://github.com/ohcnetwork/care_fe/issues/13153",0.74013984,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"\u003Cimg width=\"670\" height=\"770\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/308a3db2-0518-4e41-bb5e-5f8a44269baa\" />\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",[],12889,"Add * mark on required fields and disable save button initially in Discount Code Sheet","2025-07-13T04:55:10Z","https://github.com/ohcnetwork/care_fe/issues/12889",0.7635384,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3199,"title":3200,"updated_at":3201,"url":3202,"score":3203},"**Describe*\nCurrently, when assigning a Location to an Encounter, users can only pick from existing Locations. This improvement will allow users to create a new Location directly within the same workflow, without leaving the Encounter form or navigating to a separate screen. This is especially helpful when all existing Locations are occupied and a new Location needs to be added immediately, ensuring a smoother and faster user experience\n\n\nhttps://github.com/user-attachments/assets/cdfd5bb3-a548-435e-b10d-4ac5349e79bb\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",[],12873,"closed","Allow users to create a new Location directly when assigning a Location to an Encounter","2025-07-14T08:14:50Z","https://github.com/ohcnetwork/care_fe/issues/12873",0.7094654,{"description":3205,"labels":3206,"number":3210,"owner":3172,"repository":3173,"state":3199,"title":3211,"updated_at":3212,"url":3213,"score":3214},"**Is your feature request related to a problem? Please Describe.**\nAdd Delete functionality for dept/team \n\nBE PRs: \nhttps://github.com/ohcnetwork/care/pull/3001\nhttps://github.com/ohcnetwork/care/pull/3010\n\nSlack Thread:\nhttps://rebuildearth.slack.com/archives/C010GQBMFJ9/p1744997508567249\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",[3207],{"name":3208,"color":3209},"stale","688388",12626,"Delete feature for organizations (Dept/Team)","2025-07-18T12:34:22Z","https://github.com/ohcnetwork/care_fe/issues/12626",0.710733,{"description":3216,"labels":3217,"number":3218,"owner":3172,"repository":3173,"state":3199,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**Describe the bug**\nWhen adding beds on the home page of Locations, it's successfully created but can only be seen using the \"map\" view. Not visible on the \"list view\"\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings' > 'Locations'\n2. Click on 'Add Location'\n3. Scroll down and add beds\n4. See that it's shown on Map view but not on List View \n\n**Expected behavior**\nBoth the list view and map view should be consistent with each other.\n\n**Video Demo**\n\nhttps://github.com/user-attachments/assets/0e9e34ae-221e-4597-9954-5d067b9a63d1\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",[],12444,"Bug: Locations page inconsistency between list and map view","2025-05-30T03:14:25Z","https://github.com/ohcnetwork/care_fe/issues/12444",0.7133589,{"description":3224,"labels":3225,"number":3226,"owner":3172,"repository":3173,"state":3199,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**Describe**\nRedesign Departments List View like tabular design of location more cleaner and less space consuming making more departments to be shown on single page\n\nCurrent Dept Design \n\n\u003Cimg width=\"1166\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/12345786-feba-4891-a7dd-c71dea35e028\" />\n\nCurrent Location list Design\n\n\u003Cimg width=\"1166\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bee6246f-fbd0-4406-bea3-5100d8eaee59\" />\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",[],12474,"Redesign Departments List View like tabular design of location","2025-06-13T12:11:38Z","https://github.com/ohcnetwork/care_fe/issues/12474",0.72476596,{"description":3232,"labels":3233,"number":3234,"owner":3172,"repository":3173,"state":3199,"title":3235,"updated_at":3236,"url":3237,"score":3238},"**Is your feature request related to a problem? Please describe.**\n- On Add Questionnaire page in encounter, there is no Back button provided for users to easily navigate to the previous page\n- Several pages in the system (e.g., Patient Detail, Encounter Detail, and similar detail views) do not provide a Back button for user navigation. This forces users to rely on the browser’s back button, which is not intuitive and may break the expected navigation flow.\n\n**Describe the solution you'd like**\nA Back button should be available, allowing users to return to the previous screen\n\n** Screenshot\n\n\u003Cimg width=\"1889\" height=\"968\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f02e5b15-2436-43e9-9bd0-2f28ea6ba4be\" />\n\n**Describe alternatives you've considered**\nA clear and concise description of any alternative solutions or features you've considered.\n\n**Additional context**\nAdd any other context or screenshots about the feature request here.\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",[],13467,"Missing Back Button on Add Questionnaire page","2025-08-25T14:28:00Z","https://github.com/ohcnetwork/care_fe/issues/13467",0.7329558,{"description":3240,"labels":3241,"number":3249,"owner":3172,"repository":3173,"state":3199,"title":3250,"updated_at":3251,"url":3252,"score":3253},"**Is your feature request related to a problem? Please describe.**\nA clear and concise description of what the problem is. Ex. I'm always frustrated when [...]\n\n**Describe the solution you'd like**\nA clear and concise description of what you want to happen.\n\n**Describe alternatives you've considered**\nA clear and concise description of any alternative solutions or features you've considered.\n\n**Additional context**\nAdd any other context or screenshots about the feature request here.\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,3245,3246],{"name":3243,"color":3244},"question","d876e3",{"name":3208,"color":3209},{"name":3247,"color":3248},"needs-triage","ededed",12098,"Make SortIndex a Generic Reusable Component not just location specfic.","2025-07-30T09:45:14Z","https://github.com/ohcnetwork/care_fe/issues/12098",0.736471,{"description":3255,"labels":3256,"number":3257,"owner":3172,"repository":3173,"state":3199,"title":3258,"updated_at":3259,"url":3260,"score":3261},"**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.74890167,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSlwHNpSk6TjQqfvki0qMbfBfuRE3R1JrNYMi62EBz8k":-1},"/ohcnetwork/care_fe/12446"]