hackforla / hackforla/HomeUniteUs

Product: Section 2 | Coordinator Dashboard Enable Bulk Assignment for Multiple Applications

Open
#892 1 comment 0 reactions 0 assignees View on GitHub
Complexity: Medium p-Feature: Dashboard Coordinator Ready for: Product Lead Role: PM size: 8pt
Dominant language
Python
Stars
45
Forks
22
Avg merge
15d 1h
Merged PRs (30d)
1

Description

## 🧩 Overview
[Provide a brief description of the feature, outlining its purpose and expected outcome see the related user story - We need to do X for Y reason.]

---

## 🧠 Problem Statement
> What problem are we solving, and why is it important?
> Example: Hosts currently lack an easy way to share information about themselves and their homes for the matching process.

---

## 🙋‍♀️ User Story
**As a** [type of user],
**I want** [some goal or capability],
**So that** [reason or value it delivers].

> Example:
> As a Host,
> I want to fill out a Profile with details about myself and my home,
> So that I can be accurately matched with a guest.

---

## 🎯 Acceptance Criteria (Definition of Done)
*Transfer information to Design to Engineering Issue to be checked off*
*These high-level criteria will be detailed further in Design and Engineering handoff templates*
- Clear list of conditions to be met for this feature to be considered complete.
- Each should be testable and specific.

> Example:
> - [ ] Host can access the Profile from the dashboard.
> - [ ] All required profile questions display correctly.
> - [ ] Hosts can save progress and resume later.
> - [ ] The data is stored in the appropriate backend repository.

---

## 🔍 Context / Background
> Any relevant links, decisions, research, or history.

- Research Summary: [link]
- Previous Discovery Work: [link to doc]
- Related Epics or Projects: [link]

---

## 🖼️ Design Notes (Preliminary)
- Is this feature ready for design work? Yes / No
- Any ideas, inspiration, or existing patterns that should be considered?
> Example: Use form components from the design system; style similar to Guest Intake Form.

---

## 📌 Scope Considerations (In/Out Scope)
- [Feature List](https://docs.google.com/spreadsheets/d/1uM287TOz20jnXPS4kRe0Dt5GlhnPbNRYBHHOxcamCJ0/edit?gid=343529642#gid=343529642) *Add/Update Feature List*
- [ ] Added to [Feature List](https://docs.google.com/spreadsheets/d/1uM287TOz20jnXPS4kRe0Dt5GlhnPbNRYBHHOxcamCJ0/edit?gid=343529642#gid=343529642) and completed information accordingly

**In Scope:**
- Initial release of host profile questions and storage.

**Out of Scope (future or separate stories):**
- Matching algorithm
- Admin dashboard for reviewing profiles

---

## 🛑 Constraints / Risks / Workflow Dependency
*(Compliance / Regulatory information will be captured in the Feature List, this should be specific to the feature, where applicable)
- Known data dependencies?
- Technical limitations?

> Example: We must collect data in a way that meets GDPR and local data privacy laws.

---

### Action Items
- Assign and Prep
- [ ] Product Manager: Understand, draft User Story and self-assign
- [ ] Product Manager: Conduct the necessary research (if applicable), clarify any questions
- [ ] Product Manager: Work with PM team/lead to clarify any questions about the User Story
- [ ] Product Manager: Work with Product Team Lead to assign the appropriate size & complexity
- [ ] Product Manager/Lead: determine if work should be split into multiple issues, if so, create issue(s) and link them in this issue (if applicable) or create as standalone.
- Draft and Review:
- [ ] Product Manager: Change Issue Status to "In Progress"
- [ ] Product Manager: Draft User Story
- [ ] Product Manager: Change Issue Status to "For Review/Feedback Needed"
- [ ] Product Manager: Add Label "Ready for: Design Peer Review"
- [ ] Product 1st Level/Peer Review: Review to ensure the story captures the objective/goal of the feature to be developed and provides adequate for Design and Dev. Provide comment(s) in the comment section of the issue and tag assignee.
- [ ] Product 1st Level/Peer Reviewer: Change Issue Status to "Questions/Clarification" and add label "Ready for Product.....Persona"
- [ ] Product Manager (Assignee): Change Issue Status to "In Progress"
- [ ] Product Manager (Assignee): Review issue comment(s) and resolve accordingly
- [ ] Repeat above steps until all comments are resolved
- [ ] Product 1st Level/Peer Reviewer: Change Issue Status to "For Review/Feedback Needed" and add label "Ready for: Product Lead"
- [ ] 2nd final/Product Lead: Review and provide feedback (if any) in comment section below, add label "Ready for Product...Persona"
- [ ] Repeat above steps until all comments are resolved

---

### 🔗 Related Tickets
- Add all related ticket(s) as sub-issues (add picture)
- Design Ticket: [link]
- Engineering Ticket: [link]
- QA Test Plan: [link]

---
### 📎 Resources & References

- Existing Research: [Link]
- Brand Guidelines / Design System: [Link]
- Previous or Related Designs: [Link]

---

### Overview
Currently, Coordinators can assign applications one by one (see #889 -- useful but can also lead to inefficiencies and wasted manual work time. A bulk assignment feature will allow multiple applications to be selected and assigned in a single action, improving workflow efficiency.

**User Story**
As a Coordinator, I want to assign multiple applications at once, so that I can process applications faster without repetitive manual work.

**High-Level Approach**
Enable bulk selection checkboxes for multiple applications.
Add a “Bulk Assign” button that allows assignment to a selected Coordinator.
Ensure real-time updates so changes reflect immediately in the dashboard.

**Acceptance Criteria**
- [ ] Coordinators can select multiple applications using checkboxes.
- [ ] Clicking “Bulk Assign” opens a modal or dropdown with available Coordinators.
- [ ] Selecting a Coordinator assigns all selected applications at once.
- [ ] Assignments update in real-time without requiring a page refresh.

### Resources/Instructions
**Considerations**
Permissions: Ensure only authorized users can bulk-assign cases.
Notifications: Should Coordinators receive a confirmation message for bulk assignments?

**Design**
Wireframes for bulk selection UI (checkboxes & “Bulk Assign” button). 1pt 4-6 hrs
Define error handling flow (e.g., if an assignment fails for some applications). 1 pt 4-6 hrs

**Engineering**
Implement bulk assignment selection UI (checkboxes, bulk action button) 2 pt 7-12 hrs
Backend support for bulk assignment logic (processing multiple assignments in one request) 2 pt 7-12 hrs
Ensure real-time updates for bulk assignments (dashboard updates without reload) 1 pt 4-6 hrs

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.