Statuses can be used to represent various phases an item goes through in your development cycle. Phases could be ideation, development, testing, and deployment. So the first step before creating statuses is identifying what phases your team has.

Though Freshrelease was built for teams that build and shipping software, the product works great for other business teams like marketing, operation, etc looking to adopt the agile way of doing things. Let's see how to set up statuses for various teams.

For software development teams

Statuses could be,

1. Open

2. Dev in progress

3. Code review

4. In testing

5. Done or Shipped or Close

Your workflow could be,

1. Open -> Dev in progress

2. Dev in progress -> Code review

3. Code review -> In testing or Dev in progress (in case developers need to fix code reviews)

4. In testing -> Closed or Dev in progress (in case developers need to work bugs from testing phase)

For marketing teams

Statuses could be,

1. Open

2. Draft

3. Under review

4. Live on website

5. Closed

Your workflow could be,

1. Open -> Draft

2. Draft -> Under review

3. Under review -> Live on website or Draft (in case content writers have to fix some review comments)

4. Live on website -> Closed

For operations teams

Statuses could be

1. Open

2. In Progress

4. Approval

5. Rejected

6. Closed

Your workflow could be

1. Open -> In progress

2. In progress -> Approval

4. Approval -> Closed or Rejected (in case approval is rejected)

5. Rejected -> In progress (from rejected phase team members can fix and re-submit for approval)

Once a status is created, you can't use it unless you put it inside a workflow. All statuses in Freshrelease are put into one of the 3 categories. They are Work yet to start, Work in progress and Work done

What are status categories?

Status categories help to identify which phase of workflow an item is currently in. Freshrelease has 3 broad categories that all statuses fall under.

1. Yet to start

2. Work in progress

3. Completed

While creating a status, users must also set the category.

Why do we need status categories?

Since statuses are customizable and can change for every team, it becomes hard to identify when work was started and when work was completed for an item. Status categories help to solve this problem and allow Freshrelease to calculate some important metrics like "work start date" and "resolved date".

When someone moves an item to a status of "Work in progress" category, "work start date" is captured and "resolved date" is captured when someone moves an item to a status of "Completed" category.

Next: Making statuses a part of your workflow