Organize Tasks

[PaulJohannFlade]

Organize Tasks

Value Proposition

As a family member,

I want to organise tasks by priority, category, and assigned family member,

so that I can manage tasks more efficiently by focusing on urgent tasks, grouping similar tasks, and knowing who is responsible for what.

Description

Acceptance Criteria

• A navigation link "Filter" icon is displayed on the home page.
• Ability to filter tasks in modal window with the headline "Filter" based on
  • priority levels (e.g., "High", "Medium", "Low"),
  • category, providing a cohesive view where tasks belonging to the same category (e.g., "Cleaning"),
  • assigned member
• The interface for filtering tasks is intuitive and straightforward, with clear indications of the currently applied organisational criteria (e.g., filtered by priority, by category, assigned member).
• Users can easily switch between different organisational views (priority, category, assigned member) without losing context or needing to navigate away from the main task page.
• Display appropriate message, when no filter criteria is meet.
• User can clear one, or more or all the filter.

Tasks

• [ ] create feature branch feature/organise-task-by-priority
• [ ] create FilterTasksForm component with the headline Filter and filter options : Priority, Category, Assigned Members and a button Apply to filter the tasks and a Clear all button to clear the filter
• [ ] create a button for Filter icon in the home page, implement logic so that clicking on the Filter icon opens up a modal window by rendering FilterTasksForm component in Modal component
• [ ] implement the logic to display that list of tasks in main page, upon filter selection, when no tasks meet the selection criteria display appropriate message.
• [ ] implement the logic to clear the filter selection: can clear individual filter
• [ ] implement logic to "Clear all" filter to remove/cancel the filter selection
• [ ] style the Filter icon when filter is set

[FelineHuhn]

Great user story, clearly formulated and structured! 🤩 Some thoughts of mine:

Wireframes:

• The ckeckboxes on each task are implemented in the user story before, right?
• I'm not sure if it's very intuitive for the user to remove all filters when they press the filter icon again. What do you think?

Acceptance criteria:

• Since the filter form opens as a modal on the same page and the user is not navigated to another page, the filter would be a button rather than a link according to semantics. But you already mentioned it right as task.
• Have you thought about a "cancel" button (or "x") in case the user doesn't want to set a filter after all?

[SwethaJanardhana]

Checkbox is for the "Mark as Completed" user story that is already existing.

"Cancel" button for the modal window not needed for now for consistency , user can click on the backdrop to close the modal window. We'll work on the "cancel" button later since we have used the same design for other user stories.

[FelineHuhn]

Ah great, I remember now! :) You should implement the checkboxes in the other two user stories, since they are missing there. :)