Stages

New: New tasks would be the client’s current requests-anything old or without description stays in New as a "Backlog" task, tasks stay in New until they actually begin getting worked on. Tasks in new should not have any tags on them, as all questions should be answered by the time a task is in this stage. 

Waiting Info: If the task needs additional feedback from the customer, we move the task to "Waiting Info."

On Deck: When a task has all the details needed to begin work, it is moved to "On Deck." Usually, the task will be assigned at this stage, but dev tasks may be unassigned depending on dev workload.  

In Process: Tasks move to "In Process" when work actually begins. It is important to use the timer function to begin a timesheet when a task is moved to "In Process."

Under Review: Task moves to "Under Review" when Dev work is completed and if the task is simple, straightforward, or otherwise urgent, it could potentially be deployed directly to staging then prod, and task is then reassigned to the consultant moved to Done. Otherwise, when a dev or consultant moves the task from In Progress to In Review, it would be assigned automatically back to the consultant for QA and Testing. Task stays in "Under Review" until shown and tested to/by the customer, or is otherwise ready for deployment (such as simple/straight-forward tasks). Once customer approves task, we leave in "Under Review," assign to dev, and use the Green notification boolean to indicate the task is ready for deployment. Note: Currently, tasks to deploy will be assigned to Andrew, though this will change in the near future. 

Done (folded stage): Once prod deploy is complete, green notification icon is removed, task is assigned back to Consultant and moved to Done.

General Support: This stage is for recurring or general tasks, to log time for non-task related email responses, research into customer questions, support, and calls to the customer. 

Red/Green Notifications: As listed above, when a task is ready for deployment, the Green "dot" indicator should be used. If a task needs an Internal Review, the Red indicator should be used, and the task assigned to the person who needs to review the task. In addition to the Red indicator, a log note should be made, @ing the internal user of what is needed from the review. 

Assignees:

We should be aware of task assignees. Ideally, there is only one assignee at any given time. The person the task is assigned to indicates who is needed to look at, review, discuss a task, or respond to a log note. Of course there is nuance to this, and there may be times multiple people are assigned to the same task. 

Tags

There are several tags that can and should be used where applicable:

"Development" tag will set a deadline 7 days from the time the task is saved with this tag. 

"Urgent" will set a same-day deadline once the task is saved with this tag.

"Bug" will set a deadline two days from the time the task is saved with this tag. 

"Training" will set a deadline two days from the time the task is saved with this tag.

Note for future discussion: Cancelled would be its own stage, placed to the right of Done, and should be folded to cut down on clutter. Stage could be eliminated and a cancelled tag be used, putting the task in New or Backlog in case it needs revisited in the future. Cancelled tasks should have a log note detailing when the task was discussed and agreed to be cancelled by the customer. 

Note: Saved Favorite filters/default filters could be used to quickly show grouped by selections, or to include/exclude specific tags.