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
Categories allow for consistency across doc types while keeping flexibility at the lower status level.
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
Create a custom status
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.
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.
- To prioritize
- To discover/spec
- To design
- Ready to dev
- To do
- In progress
- To QA
- QA passed
- Loop closed