Velocity Chart in ClickUp

The legacy Velocity Chart in ClickUp helps Agile teams understand how much work they complete in each sprint so they can plan future work with confidence. This guide explains how to enable, configure, and interpret the chart, plus important limitations and troubleshooting tips.

What is the Velocity Chart in ClickUp?

The Velocity Chart is a Scrum reporting tool that displays the amount of work finished during each sprint. In this legacy ClickUp feature, velocity is measured using the number of Story Points or tasks completed per sprint.

Use this chart to:

Track how much work your team completes in each sprint.
Estimate how much work to include in upcoming sprints.
Visualize trends in team performance over time.
Identify when scope or workflow changes affect output.

Because this is a legacy feature, it’s important to understand what is supported and how its data is calculated.

Legacy Velocity Chart and ClickUp sprints

The Velocity Chart is specifically designed to work with ClickUp sprints managed in the Sprints ClickApp. It summarizes historical sprint data so teams can adjust planning based on real performance.

In the legacy experience, the chart:

Shows completed work for each closed sprint.
Groups data by sprint name and dates.
Uses the same sprint configuration from your Space.

Because this is the legacy chart, it does not include all of the enhancements available in newer reporting tools.

Prerequisites for using the ClickUp Velocity Chart

Before you can use the Velocity Chart in ClickUp, make sure your Workspace meets the following requirements:

Enable sprints in ClickUp

Open your Workspace settings and go to ClickApps.
Find and enable the Sprints ClickApp for the Space where you manage Agile work.
Configure sprint duration, naming, and other sprint options according to your team’s process.

Use Story Points or tasks as effort units

The Velocity Chart supports two effort units in ClickUp:

Story Points: Add the Story Points field to tasks and estimate effort numerically.
Task count: Use the number of completed tasks per sprint when Story Points are not used.

Choosing one standard unit in your Space keeps the Velocity Chart consistent and easier to interpret.

Organize work into sprints

To populate the Velocity Chart, all relevant tasks must be assigned to a sprint. In ClickUp, you can do this using sprint Lists or sprint tags, depending on how your Space is configured with the Sprints ClickApp.

How to open the Velocity Chart in ClickUp

The legacy Velocity Chart is available in the Velocity Chart (Legacy) ClickUp help article context. If it is enabled for your Workspace, you can access it from the reporting or dashboard area associated with legacy Agile reports.

Once open, you will see a line or bar visualization that summarizes your team’s completed work per sprint.

Configure your ClickUp Velocity Chart view

The legacy chart includes several controls that let you fine-tune what is displayed. While the exact interface may differ depending on your Workspace setup, you will typically adjust:

Select location or Space

Filter the Velocity Chart to show data from a specific Space or location in ClickUp where your sprints live. This ensures that only tasks from the correct project or team are included.

Choose date range or sprint range

Select which sprints or time range to include in the chart. You might display:

The last few sprints to focus on recent performance.
A larger set of historic sprints to review long-term trends.

Set the effort unit in ClickUp

Decide how to measure work on the Velocity Chart:

Story Points for teams that estimate work in points.
Task count for simpler tracking based on completed items.

Changing this setting updates all data on the chart accordingly.

How velocity is calculated in ClickUp

The legacy Velocity Chart in ClickUp calculates velocity by summing completed work for each sprint. The calculation method depends on the unit you choose.

Velocity using Story Points

When using Story Points, the chart adds up the Story Points from tasks that meet both of these conditions:

The task is assigned to a sprint included in the chart.
The task is moved to a completed status before or on the sprint end date.

The result is the total Story Points completed per sprint.

Velocity using task count

When using task count, the chart counts the number of tasks that:

Belong to a sprint in the selected range.
Reach a completed status before or on the sprint end date.

This produces the number of completed tasks per sprint represented on the chart.

How to read the Velocity Chart in ClickUp

The ClickUp Velocity Chart (legacy) presents velocity across several sprints, allowing you to compare performance.

Key elements on the chart

X-axis: Represents sprints, usually labeled by sprint name and dates.
Y-axis: Shows the amount of work (Story Points or tasks) completed.
Bars or points: Each bar or data point indicates the total completed work for that sprint.

Identify trends in ClickUp velocity

Look for patterns across sprints:

Stable velocity: Similar values for multiple sprints suggest predictable capacity.
Increasing velocity: May indicate improved processes or higher capacity.
Decreasing velocity: Could point to blockers, scope changes, or estimation issues.
Highly variable velocity: Often signals inconsistent sprint scope or incomplete work.

These patterns help Scrum Masters and Product Owners make better planning decisions in ClickUp.

Best practices for using the Velocity Chart in ClickUp

To get reliable insights from this legacy chart, keep these practices in mind:

Keep sprint lengths consistent so velocity comparisons are meaningful.
Use the same estimation unit across all sprints in ClickUp.
Finish work within the sprint to avoid carrying over a large percentage of tasks.
Close sprints on time so the chart reflects an accurate snapshot of completed work.
Review the chart regularly as part of sprint review or retrospective meetings.

Limitations of the legacy Velocity Chart in ClickUp

Because this is a legacy ClickUp feature, be aware of some common limitations:

It may not support the newest reporting or dashboard improvements.
Configuration options can be more limited than newer ClickUp reporting tools.
Some edge cases, such as tasks moved between sprints, may affect historical velocity values.

If your team needs more advanced analytics, you can supplement this legacy chart with updated reports or third-party analytics tools.

Troubleshooting Velocity Chart issues in ClickUp

If the Velocity Chart does not look correct in ClickUp, check the following areas.

Chart shows no data

Confirm that sprints exist in the selected Space or location.
Verify that tasks are assigned to those sprints.
Make sure at least some tasks are in a completed status before the sprint end date.

Velocity seems too low or too high

Review whether the correct effort unit (Story Points or tasks) is selected.
Check if tasks were closed after the sprint ended; these will not be counted.
Ensure tasks are not incorrectly assigned to multiple sprints.

Inconsistent results across sprints

Confirm sprint dates are aligned and not overlapping.
Check for changes in estimation practices that may affect Story Points.
Review major team or scope changes that may impact throughput.

Next steps and additional resources

To deepen your understanding of the legacy Velocity Chart, review the official documentation directly from ClickUp: Velocity Chart (Legacy) help article.

If you want help optimizing your Agile setup, integrations, or reporting around ClickUp, you can also explore expert consulting resources like Consultevo.

By enabling sprints, estimating work consistently, and understanding how the legacy Velocity Chart in ClickUp calculates and displays data, your team can make better decisions about capacity and improve sprint planning over time.

Need Help With ClickUp?

If you want expert help building, automating, or scaling your ClickUp workspace, work with ConsultEvo — trusted ClickUp Solution Partners.

Get Help

“`