Created: Mar 23, 2020 12:26 PM
Priority: P2
Status: Not Started
Timeline: Mar 23, 2020 → Mar 24, 2020
Type: Task 🔨
Overview
Problem statement
Describe the problem you're trying to solve by doing this work.
Supervisors create many profiles every day. We want to make populating a profile as easy and fast as possible (data entry should be as easy as possible).
Proposed work
High-level overview of what we're building and why we think it will solve the problem.
Users (namely supervisors) should be able to tab through options and automatically populate fields.
For example, if I could tab to "Grade" and type "S", if senior could automatically populate, then I could tab to Gender and hit "M" for male and tab on. As it is now, I need to click on the box and the option each time.
Success criteria
The criteria that must be met in order to consider this project a success.
Inputs are properly tab-indexed (clicking tab goes to the next input and focuses on it).
Select inputs enable users to type content of the select to pre-fill it.
You can fill out the whole profile without lifting your hands from the keyboard.
Filling out a new profile should take no more than 30 seconds.
User stories
How the product should work for various user types.
User type 1
User type 2
Scope
Requirements
Current project requirements.
Future work
Future requirements.
Non-requirements
List anything that is out of scope.
Designs
Include designs here or add directly to the Requirements or User Stories sections.
Alternatives considered
List any alternatives you considered to this approach. Explain why they weren't used.
Related documents
Include links to other pages as necessary (e.g. technical design doc, project proposal, etc.)
Polish profile input
Created: Mar 23, 2020 12:26 PM Priority: P2 Status: Not Started Timeline: Mar 23, 2020 → Mar 24, 2020 Type: Task 🔨
Overview
Problem statement
Describe the problem you're trying to solve by doing this work.
Supervisors create many profiles every day. We want to make populating a profile as easy and fast as possible (data entry should be as easy as possible).
Proposed work
High-level overview of what we're building and why we think it will solve the problem.
Users (namely supervisors) should be able to tab through options and automatically populate fields.
Success criteria
The criteria that must be met in order to consider this project a success.
tabgoes to the next input and focuses on it).User stories
How the product should work for various user types.
User type 1
User type 2
Scope
Requirements
Current project requirements.
Future work
Future requirements.
Non-requirements
List anything that is out of scope.
Designs
Include designs here or add directly to the Requirements or User Stories sections.
Alternatives considered
List any alternatives you considered to this approach. Explain why they weren't used.
Related documents
Include links to other pages as necessary (e.g. technical design doc, project proposal, etc.)