Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Tasks show users actions that need to be completed in relation to a document. These tasks would involve approving various reports and plans created by a teacher. Multiple users may have the ability to review the same document, so it is important for the user to understand if another team member has already approved the document. There are some teacher tasks also for Contracts. The admin approves and the teacher makes active. Separate place/section for app?

Design Link:

Overview

User Story

  • As an educator viewing the mobile app, I want to see a list of all tasks I need to complete, so I know what items need my attention

UI

Acceptance Criteria

  • Given admin user has r

User Story

  • As an educator viewing the Tasks area, I want to remove tasks, so I can focus on the tasks I need to complete (Show example/reference when it is removed from this area what happens to the All Tab)

UI

Acceptance Criteria

  • Given admin user has r

User Story

  • As an Admin viewing the Task tab, I need to view the details of each of documents sent to me so that I can approve the request and respond to the teacher who sent it. (Is this a flow to Review Docs?)

UI

Acceptance Criteria

  • Given admin user has r

User Story

  • As a teacher viewing the Task tab, I need to make a contract active so that I can have it in place to help the student with developing behavior skills.

  • No labels