πŸ”€Statuses

Automating the automatable

Some tasks are worth your time, but manually updating ticket statuses isn't. Cycle workflows do just that: Updating the status of related docs, when their parent's status changes.

Let's see how this can help you consistently close the loop with customers.

To setup workflows, go to workspace settings > workflows

Table of content

  1. Frequent questions

Introduction

Each doc type can have its own statuses. These statuses can be shared across doc types and are grouped into four categories:

  • Not started

  • Started

  • Completed

  • Canceled

Categories allow for consistency across doc types while keeping flexibility at the lower status level.

To understand better how you can close the loop internally & externally, please read this article. In a nutshell, you don't update insights's statuses: they follow the status of the feature they're linked to.

1 insight can have only 1 status per status category.

Make sure your delivery statuses in Cycle are in the "Started" category for a smooth process.

We recommend having only delivery statuses in the "In Progress" category and no things like "Ready to dev".

We recommend keeping feedback & insights statuses as is and only modifying/creating new statuses for features, problems, and other types you might have created.

Create a custom status

When you create a doc type, it will automatically get a progress status for each category. But some doc types have more steps before passing from one category to another.

Here's how to create a custom status:

  1. Click the "+" icon next to the progress category

  2. Name your custom status

  3. Link it to the doc type that should get this custom status

Editing a status and automatic updates

To update a doc's status, hit β€œctrl+shift+s” or click on the doc's status property to change it manually.

For insights, status will automatically update based on the Features they’re linked to. It means that when a 🌱 Feature is set as "shipped", all related insights will automatically move to β€œshipped”. This is a great way to let customer-facing teams know they can close the loop with customers that provided insights for this Feature.

Status suggestion

Here is a workflow suggestion created by our power users and ourselves.

The goal is to inspire you, feel free to adapt them to your needs.

They are in line and compatible with the properties' suggestions and the views' suggestions.

Not started

  • To prioritize

  • To discover/spec

  • To design

  • Ready to dev

  • To do

Started

  • In progress

  • Blocked

  • To QA

  • QA passed

Completed

  • Live

  • Loop closed

Canceled

  • Canceled

Frequent questions

If I have 1 piece of feedback with 2 insights linked to 2 separate features:

If I change the feedback status, will it change another status as well?

No. You can think about the feedback status as "did you create the relevant insights or not?" Once you have created all insights you needed, then the feedback status should be processed.

Also, nothing will change your feedback status.

How to change insights' statuses?

You can't. Insights will automatically follow the status category of the feature linked to it.

In the example below, 🌱 is the emoji for a feature. Here is the potential lifecycle of an insight:

  • Insight created but not linked to a feature: status "to link"

  • Insight linked to a feature that is anything between "to prioritize" & "to do": "to do"

  • Insight linked to a feature that is anything between "in progress" & "QA passed": "in progress"

  • Insight linked to a feature that is anything between "shipped" & "success": "shipped"

  • Insight linked to a feature that is "canceled": "canceled"

Then we have 1 special built-in status called "Loop closed": the insight will have this status if the feature has this one. This status is used to close the loop with your customers.

Last updated