📋Views
Multiple ways to display information.
Last updated
Multiple ways to display information.
Last updated
A view is a filtered and structured way to visualize your Cycle Feedback, Insights, or Roadmap. You can create your own views by choosing which doc types to display, applying filters, and grouping docs by properties.
Only "Makers" can create and edit views. Go to the "Create and edit views" section to learn more.
In this section we'll see how to work in views.
You'll find all your views in a breadcrumb. From any view, just click on "Views" to get back there.
Click on the view name to switch views quickly.
Pro tip: Right-click on Feedback, Insights, Roadmap to go directly to a certain view.
Here's an example of a view with all "Small" Features grouped by "Status". Click the "+" icon.
Only "Makers" can create views. If you are the first to join yourn workspace, you're a "Maker" by default. If not, ask a Maker to change your role.
You can also create a view from the side bar.
Click on the view name to edit this view. You can also rename a view or add a description to it by clicking the view's name.
There are four main ways to organize your content inside a view. You can use filters, group bys, and subgroups (swimlanes). You can also decide which properties you want to display.
You can display the insights linked to each Doc type. Click on the 💡 icon to see the related insights! To display insights, open the settings of a view, under “properties,” toggle “💡 Insights”.
You can also rearrange your views. Just drag & drop them.
Some views can be pretty similar to one another. No need to re-create them from scratch.
When a "Maker" creates a view, they can choose between a kanban or list view.
Kanban: Display docs in horizontal columns. Usually, each column holds docs from the same property value.
List: Display docs in a vertical list.
Swimlane: Combine a kanban and list view. This works great for roadmaps: See docs grouped in columns by a time horizon, while also splitting the view vertically by a key product area for example.
The feedback Inbox is a list view, grouped by status.
When a list view is grouped by a property, you can expand and collapse groups by clicking the arrow in the top left corner of the group. This is a great way to declutter a view.
Drag and drop multiple docs from one place to another. The corresponding property will automatically update for every selected doc.
You can also achieve this by holding the "shift" key and clicking on the docs you wish, then use the editing menu at the bottom of your screen to edit the docs' property values.
Just click on “Export in CSV” and get the file by email.
Similarly, click on "Star" to keep at hand your favorite views.
Here are the views created by our power users and ourselves. The goal is to inspire you, you'll probably not use them all on a weekly basis.
Feel free to adapt them to your needs. They are in line and compatible with the properties' suggestions and the workflow suggestion.
Inboxes split by feedback type
List view
Filtered by "Feedback type"
Grouped by status
1 view for each Product Manager
List view
Filtered on a certain squad
Grouped by status
Customer voice - this is a default
Kanban view
Grouped by Importance (or another relevant property)
Sub-grouped by Feature (or another relevant doc type)
Insight pipeline
Kanban view
Grouped by status
Key Customer X (or multiple key customers in 1 view)
Kanban view
Filtered by company
Grouped by status
Recent insights
List view
That's it! The most recent insights will automatically be on top of the list.
All features (Features + Improvements)
List view
Doc types: Epic & stories (or just features or relevant doc types for you)
That's it!
High-level roadmap (Now soon later for Features)
Kanban view
Doc type: Epic (or just features or relevant doc types for you)
Grouped by: Timing
Delivery pipeline
Kanban view
Doc type: Bugs, features & Improvements (or just features or relevant doc types for you)
Grouped by: status (hide the ones not relevant for you for instance hide "to do" and "canceled")
Bugs backlog - grouped by importance
Kanban view
Doc type: Bug
Filtered by: status is not any of "Completed" or "Canceled"
Grouped by: Importance
Bugs, Improvements, and features grouped by Product Area
Kanban view
Doc type: Bugs, stories & Improvements (or just features or relevant doc types for you)
Filtered by: Status is not any of "Completed" or "Canceled"
Grouped by: Product Area
Backlog (Epic/story ready to dev)
Kanban view
Doc types: Epic & stories (or just features or relevant doc types for you)
Filtered by: status is "To dev"
Grouped by: Timeline
Current topic/engineer
Kanban view
Doc type: the most granular doc you'd like to have a view on
Filtered by status is: [the ones you consider as being relevant in the status category "Started"]
Grouped by Assignee (make sure your engineers assign themselves to docs they're working on)
NB: Feedback & Insights’ assignees should be the ones giving the feedback, but for epics/stories we put engineers as assignees.
