From 1c2f82f069f72086685f3374d940e0e92f2d3919 Mon Sep 17 00:00:00 2001 From: Guo-William Date: Wed, 28 Feb 2018 22:07:31 -0500 Subject: [PATCH] Add README stuff --- README.md | 29 ++++++++++++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 187cdee..8f1f1a4 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,33 @@ # Tasktracker -decisions made: +decisions made for task2: +Users can only become managers during registration time +Reason: I ran out of time to make it nicer. If I had time I would make it +so that a manager can elevate one of their managees to a manager position. While +remaining a manager of them still. Users can still become managers at registration +time. + +Cannot manage your manager or other managers managees. Reasoning: The president +shouldn't be managed by a junior developer lol. + +One manager per user Reasoning: keep the hierarchy clear so that communication +is easy and management doesn't have to fight each other for control of user +resurces + +Many managees per user + +It is possible to unmanage a user + +To access the management dashboard I put a link to the user index page +on the nav bar. + +To access the dashboard for all tasks related to a managers team I put a +link on the nav bar "Team Board" + +Added a nav link back to the regular task index "Task Board" + + +decisions made for tasks1: Users will have an email and username. The email is for logging in but the username is for assignee purposes. We do not need the users' name because it's not necessary for task assignment. Added unique constraints on both