Card feeds and boards are a good way to track important items. They are often used to track the progress of a sprint (or multiple sprints combined in one), overdue items, security items, personal TODOs, etc.
Add a Cards feed or a board to a dashboard
Click on the Add insight button down the dropdown on the top right of any dashboard, then select the type of cards you wish to create (this can be changed later).
Select the card type
Boards: Boards are often used to showcase items (Pull Requests, Issues, Bugs…) assigned to specific projects or users and organized based on the priorities set by the organization (due date, project significance, etc.). It helps visualize a series of items organized by stage or date.
Cards feed: A Cards feed is a more detailed view of a particular item placed on a board. Their role is to provide granular information at a project or task level for the team or individuals.
Configure Filters for your cards
You can apply AND / OR filters to narrow down the list of cards appearing in your insight.
Apply filters on card feeds
Card feeds only require one set of filters to select the cards appearing in the feed.
Apply filters on boards
Boards have one set of filters per column for detailed filtering.
You can narrow down a view at a board level further by applying an additional filter. For example, you can use this option if you want your entire team to use the same board but want to see what is assigned to a particular team member.
Change cards sorting
By default, card feeds and board columns are sorted by Due date. The sorting can be changed to one of the following fields Due date, Creation date, Merge date, Last update date.
For boards: click the sort icon in the header of each column to choose the sorting option.
For cards feed: click the sort icon in the header of the insight or the sorting dropdown in the right part of your screen to choose the sorting option.
Note that sorting can be changed directly from the dashboards thanks to the sorting icon located at the top of each card insight.
Document the cards
Insight can be complex to understand by others, so having proper documentation is important.
The documentation should explain the purpose of the insight (“Why do we track this metric in the team?”), provide some highlights about its configuration (e.g. “Showing data labeled as a bug over the last 12 months”), and explain the best way to read it (e.g. “More than 15 bugs raised per week would be considered a warning for the team”). Doing so will guarantee that the insight remains useful and readable to others at all times.
To do so, you can set the following elements:
Title (mandatory): a short and self-explanatory title
One-liner description (recommended): a short description that is displayed when browsing insights in collections.
Full documentation (recommended): exhaustive documentation regarding the goals, configurations, or reading tips about the insight. The full documentation can be written and formatted using markdown.
The full documentation can also be disabled, in which case the (?) tooltip near the insight title on the dashboard will remain hidden. Even when disabled, the documentation can still be accessed from the insight configuration.