The custom chart widget is the most flexible and powerful charting option inside Teamhood. But with power comes uncertainty on how to harness it. In this article, we provide common use case examples to help you better understand how to configure and when to use custom charts.
Widgets are the building blocks of Teamhood’s dashboards.
For this simple data visualization donut chart is more than enough. Our goal is to see how much tracked time we will soon be billing to our clients as an agency. We have used status type for higher level grouping as the X axis and Total logged time as Y axis.
X-axis: Status type
Y-axis: Total logged time

Two bar charts will do the job here. Choose the Created On field as the main axis for first chart and the Completed On field as the main axis for the second chart. Both charts should filter some recent period, here we have chosen a rolling range filter for the current month. We have also selected weekly breakdown instead of monthly in the chart settings.
First chart
X-axis: Created On
X-axis period: Weekly
Y-axis: Item count
Second chart
X-axis: Completed On
X-axis period: Weekly
Y-axis: Item count

You can also create a yearly scale with a monthly breakdown to check whether your team’s ability to close support tickets remains stable or is getting better.
For this case, we will use a Scatter plot chart and select estimation as the X axis, while total logged time will be used as Y axis. Such a chart gives us insight how accurate are we. It also visualizes the outliers in the extreme cases.
X-axis: Estimation
Y-axis: Total logged time

To have a high-level overview and understand how many items you have in each workflow stage, we will use a Bar chart. For the X axis, we chose boards, and for the Y axis item count. Then grouping is by status with stacking option turned on.
X-axis: Board
Y-axis: Item count
Grouping: Status
Stacking: Yes

Once more we will use a bar chart with X axis as an assignee field and the Y axis as item count. For grouping we have chosen status and turned on the stacking option. Neat and simple quick overview of how loaded are our colleagues.
X-axis: Assignee
Y-axis: Item count
Grouping: Status type
Stacking: Yes

This example involves having a custom field called “Impact“. It is an option field and it is used to measure how impactful the item is to the goals or projects. To measure such item breakdown over time we will use line chart option with the X axis as Completed On field, the Y axis period as weekly, and group by Impact custom field.
X-axis: Completed On
X-axis period: Weekly
Y-axis: Item count
Group by: Impact

Join the Teamhood coach for a more detailed explanation.
Need help to set up your charts or advice what’s the best way to measure things around Teamhood?