Table of Contents

Statuses

Making sure statuses are up to date within Wrike projects and tasks is a critical step in making sure all eCornell users in Wrike can stay up to date on a projects current process. Updating statuses within Wrike is also a good way of making sure you as an individual user has a refined and straightforward experience when using Wrike for your everyday tasks.

Multiple Ways to Update Status

In Wrike there are multiple ways that a user can edit/update statuses. If looking at an entire project, and trying to bring all statuses up to date, it is recommended to do so by using either the "Table View" or the "Gantt View". The table view is recommended for a project thats dates are already up to date, and the gantt view would best be used when needing to update dates in conjunction with statuses.

Here is an example of how a user could configure their columns in the "Table View" in order to easily update a project's statuses:

Note: The same columns could be activated for when using the "Gantt View", just keeping in mind the fact that there will be less visual "real estate" given to the columns in the gantt view.

Workflows

Workflows in Wrike are the individual statuses, and the order in which they are presented to users, on each task within the system.

There are multiple workflows within the eCornell Wrike account. Most of the workflows are for unique processes that are carried out for unique task development needs, or for specific groups or teams within the entire organization. However, the majority of the tasks within Wrike will use the "Default Workflow".

Default Workflow Specifics

The default workflow houses the standard set of statuses most eCornell users will be familiar with. Here is a screenshot of the workflow and it's statuses:

Here is a breakdown of what is meant by each one of those statuses:

  • Planned: A task is in the system and projected to completed at some stage of the project's development.
  • To Do: A task has been determined as ready to start, and can now be started by the task's assignee.
  • In Progress: The task's assignee has begun the work involved in completing the task.
  • Ready for Review: The assignee has completed the work for a task, and is ready for that work to be verified by the appropriate personnel.
  • Waiting for Info: A task assignee, or assigner, requires more information from an outside party or team member in order to continue any progress on the task.
  • Waiting for Resources: The task requires additional resources to be found and assigned in order to be completed.
  • On Hold: A task that is assumed to be completed at some stage of development, however cannot be progressed at the given time due to outside circumstances.
  • Done: All of the work and reviews required for a task have been completed.
  • Backlog: It is unsure if this task will be necessary for the project development, but it's need will be determined at a later date.
  • Not Applicable: A task has been determined as not needed for a project, but is being kept in the project (rather than deleted/removed) in case of future changes, or for the sake of documentation and record keeping.

Status Categories

Note: The following is for advanced users seeking deeper understanding and context of how our default workflow/statuses are constructed, and is not necessary for most users to be able to use the system appropriately.

Within workflows, certain statuses can be listed within multiple categories of status types. To demonstrate this, here is a view of how the default workflow is constructed on the backend:

The main distinction to note about the above categories are that when a task's status is in either the "Deferred" or "Cancelled" category, then it will not show up on task to-do emails, views, and reports or widgets on a user's dashboard.

How did we do?

Comments and Communication

Updating Task Start and Due Dates

Contact