Automating the automatable
Some tasks are worth your time, 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

One status property, multiple workflows

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, and canceled.
Cycle workflows
Categories allow for consistency across doc types while keeping flexibility at the lower status level.

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. 1.
    Click the "+" icon next to the progress category
  2. 2.
    Name your custom status
  3. 3.
    Link it to the doc type that should get this custom status
Create a 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 initiatives they’re linked to. It means that when an 🌱 initiative is set as "shipped", all related insights will automatically move to “shipped”. This is great way to let customer facing teams know they can close the loop with customers that provided an insight for this initiative.
If your Cycle workspace was created before the 14 of February 2022, you're probably still using a regular "status" property without automations. Read here how to migrate from the custom status property to the new built-in one.