Stats by Project

View key statistics for all your projects in one consolidated table. Compare task counts, sprint progress, team sizes, and project status across your entire workspace.

Overview

The Stats by Project page displays a summary table of all projects in your workspace. Each row represents a project with key metrics, allowing you to quickly compare project activity and identify which projects need attention.

The header shows a counter indicating how many projects are currently displayed.

Project Statistics Table

The table provides a comprehensive view of all projects with the following columns:

Project Column

Shows the project identification:

Logo: The project's avatar image
Name: The project name (truncated if too long)

Click any row to open that project in a new tab.

Progress Column

Displays a visual progress bar with percentage:

Green bar: Progress at 70% or higher
Blue bar: Progress between 30% and 69%
Yellow bar: Progress below 30%

The percentage is shown numerically beside the bar.

Tasks Column

Shows the total count of tasks in the project. This includes all tasks regardless of their workflow status.

Sprints Column

Displays the total number of sprints created in the project. This count includes all sprints, whether active, completed, or planned.

Stories Column

Shows the count of user stories in the project. User stories are high-level requirements that sprints are planned around.

Members Column

Displays how many team members are assigned to the project. This helps identify team distribution across projects.

Status Column

Shows the current project status as a colored badge:

Active: Blue badge indicating the project is currently in progress
Completed: Green badge indicating the project has been marked as finished
Archived: Gray badge indicating the project is archived

Totals Row

At the bottom of the table, a totals row aggregates the statistics:

Progress: Shows the average progress percentage across all projects
Tasks: Sum of all tasks across all projects
Sprints: Total number of sprints across all projects
Stories: Sum of all user stories across all projects
Members: Combined member count (note: members appearing in multiple projects are counted multiple times)

Searching Projects

Use the search field in the header to filter projects by name:

Type in the search field
The table updates instantly showing only matching projects
Press Escape to clear the search and show all projects

The search is case-insensitive and matches any part of the project name.

Opening a Project

Click on any project row to navigate to that project's overview page. The project opens in a new tab, allowing you to quickly review details while keeping the stats view accessible.

Empty State

When no projects exist in the workspace, an empty state message is displayed indicating there are no projects to show statistics for.

Use Cases

Project Portfolio Review

Review all projects at once to understand the current state of work across your organization. The summary statistics help identify which projects are most active and which may need additional resources.

Resource Planning

Use the members column to see how team members are distributed across projects. Combined with task counts, this helps identify projects that may be understaffed or overstaffed.

Progress Monitoring

The progress bars provide an instant visual indicator of project health. Projects with low progress (yellow bars) may need attention or scope adjustments.

Workspace Dashboard - Central workspace management
Manager Overview - Management-focused workspace view

Understanding Project Statistics

The Stats by Project view provides a comprehensive snapshot of workspace health. Understanding what each metric means helps you make better decisions.

Progress Calculation

Project progress is calculated based on:

Completed tasks: Tasks in "Done" or equivalent final workflow state
Total tasks: All tasks in the project
Formula: (Completed Tasks / Total Tasks) × 100%

Note that progress doesn't account for task effort or complexity—a simple bug fix counts the same as a major feature.

Interpreting Progress Bars

Color	Range	Meaning
Green	70-100%	On track, nearing completion
Blue	30-69%	In progress, active work
Yellow	0-29%	Early stage or potentially stalled

Best Practices for Project Statistics

Regular Review Schedule

Establish a rhythm for reviewing stats:

Daily: Quick glance at progress changes
Weekly: Identify projects needing attention
Monthly: Portfolio-level planning and resource allocation
Quarterly: Strategic review and project prioritization

Key Metrics to Watch

Pay attention to these indicators:

Low progress + high age: Project may be stalled
Many tasks + few members: Potentially understaffed
High sprint count + low progress: Possible scope creep
Few stories + many tasks: May need better organization

Using Stats for Decision Making

Resource Allocation

Use member counts and task volumes to balance workload:

Identify projects with high task-to-member ratios
Compare with progress to find bottlenecks
Consider redistributing team members
Plan hiring or contractor needs

Project Prioritization

When resources are limited:

Sort by status to focus on active projects
Review progress to identify quick wins (high progress)
Evaluate member allocation against project importance
Make informed decisions about what to pause or accelerate

Risk Identification

Spot potential problems early:

Low progress after long time: Project may be at risk
Zero sprints with many tasks: Possibly unstructured work
Single member projects: Key person dependency
Completed but active tasks: May need cleanup

Comparing Projects

Apples-to-Apples Comparison

When comparing projects, consider context:

Project age: Older projects naturally have more data
Project type: Product development vs maintenance vs R&D
Team composition: Full-time vs part-time contributors
Methodology: Scrum (sprints) vs Kanban (continuous)

Benchmarking

Establish internal benchmarks:

Track metrics over time for each project
Calculate averages for your organization
Identify outliers that need investigation
Set targets based on historical performance

Exporting Statistics Data

For external reporting or analysis:

Manual Export

Select the data in the table
Copy to spreadsheet software
Format and analyze as needed

Automated Reporting

Use GitScrum API for programmatic access
Set up webhook notifications for status changes
Integrate with business intelligence tools

Advanced Analysis Tips

Combining with Other Data

Stats by Project becomes more powerful when combined with:

Time tracking data: Hours per project
Budget information: Cost performance
Team capacity: Availability vs allocation
Historical trends: Progress over time

Custom Dashboards

For organizations needing more detailed views:

Export data regularly to a data warehouse
Create custom dashboards in BI tools
Set up automated alerts for key thresholds
Build executive summary reports

Common Questions

Why Is Progress 0%?

Projects show 0% progress when:

No tasks exist yet
All tasks are in non-completed workflow states
Tasks haven't been moved through the workflow

Why Are Member Counts High?

The totals row can show high member counts because:

The same person working on multiple projects is counted multiple times
This represents total assignments, not unique people
Use Team Members view for unique headcount

How Often Do Stats Update?

Statistics update:

Real-time for task movements and completions
Page load fetches current snapshot
No background refresh - refresh page for latest