Summary
Add a "Create task" modal, following the same pattern as the offline-activity-logging modal (frontend/src/components/LogOfflineActivityModal, issue #704), so users can create a new task without leaving their current view.
Motivation
LogOfflineActivityModal currently lets a user search for an existing task or fall back to typing a free-text name (which the backend turns into a new task on submit). There's no dedicated, lightweight flow for just creating a task — e.g. from the tasks list/panel — with its own fields (name, and whatever else a task supports beyond name: description, recurrence, category, etc. — TBD based on the backend task-creation endpoint).
Proposed approach
Reuse the modal + form-hook pattern established by LogOfflineActivityModal / useLogOfflineActivityForm:
- A
+-style entry point near the relevant task list/panel, consistent with how offline-activity logging is triggered from ActivitiesPanel.
- A
Modal (components/Modal) containing a form with client-side validation limited to obvious errors (required name, etc.), leaving business-rule validation to the backend.
- Friendly loading/success/error states, keyboard-navigable, mobile-friendly.
Open questions
- What fields does task creation need beyond name? (description, category, recurrence/schedule, etc.)
- Where should the entry point live — a dedicated tasks panel, or multiple places (e.g. also inline in
EntitySearchInput when no match is found)?
- Confirm the backend task-creation endpoint/serializer this should target.
Related
Summary
Add a "Create task" modal, following the same pattern as the offline-activity-logging modal (
frontend/src/components/LogOfflineActivityModal, issue #704), so users can create a new task without leaving their current view.Motivation
LogOfflineActivityModalcurrently lets a user search for an existing task or fall back to typing a free-text name (which the backend turns into a new task on submit). There's no dedicated, lightweight flow for just creating a task — e.g. from the tasks list/panel — with its own fields (name, and whatever else a task supports beyond name: description, recurrence, category, etc. — TBD based on the backend task-creation endpoint).Proposed approach
Reuse the modal + form-hook pattern established by
LogOfflineActivityModal/useLogOfflineActivityForm:+-style entry point near the relevant task list/panel, consistent with how offline-activity logging is triggered fromActivitiesPanel.Modal(components/Modal) containing a form with client-side validation limited to obvious errors (required name, etc.), leaving business-rule validation to the backend.Open questions
EntitySearchInputwhen no match is found)?Related