User:Nlee/Task tracker requirements

The General Gist

In implementing a task/project tracking system for the wiki, we want to be clear on our objectives. What capabilities do we want our tracker to have? Who should be able to use it, and how much should they be able to access?

There are multiple groups of people who will be using a task tracking system:

• admins - people who will be supervising organization and categorization of projects
• project leaders - the actual people who are coming up with and implementing a project
• project volunteers - people who want to pitch in on other people's projects

Functionality

What should people be able to do with the task tracking system?

Admins

Admins need to be able to "get behind the scenes" and take control of abandoned projects, etc.

• change the status of a project (pending, active, inactive, etc.)
  • current model involves only admins having this power
• edit projects
• move/recategorize project tasks

Project leaders

• create projects
• create subtasks and associate them with projects
• delete or remove subtasks from projects
• categorize subtasks (time needed, etc.)

Project volunteers

• find subtasks to do
  • should be able to easily figure out what overarching project is, who project leader is, who else is working on it, etc.
  • sorting based on time needed - minutes, hours, days, etc.
  • sorting based on level of skill needed - little/no experience, programming, language, etc.
• sign up for subtasks
• drop subtasks (un-sign up)
• mark tasks as completed