Performance Optimization

Overview

Performance issues show up as slow loads, laggy scrolling, or timeouts.

Most performance problems are caused by large datasets, heavy views, or constrained device and network resources.

Key Concepts

• Large Project: Project with many work items and linked records
• Heavy view: view with many columns, groups, and filters
• Client-side load: browser effort to render large lists

How It’s Used

Use this page when list views lag, dashboards load slowly, or updates take too long to appear.

Use it during rollout to standardize view patterns that keep performance stable.

Benefits

• Faster day-to-day navigation
• Reduced timeouts during governance reviews
• More predictable experience across large Projects

Setup Steps

1

Confirm baseline requirements

Confirm the device and browser meet recommended levels.

Related: System Requirements Related: Browser Compatibility

2

Reduce view complexity

1. Limit columns to the fields needed for the current review.
2. Avoid deep grouping when lists are large.
3. Filter to a narrower scope, such as one Segment or status set.
4. Save the configuration as a Save View.

3

Reduce browser load

1. Close unused browser tabs.
2. Restart the browser to clear long-lived memory growth.
3. Disable extensions that modify page content.

4

Isolate network vs browser issues

1. Test performance on a second network when possible.
2. Confirm service status when issues affect many teammates.

Related: Connectivity Issues

Best Practices

• Standardize shared Save Views with minimal columns.
• Keep dashboards stable and filter-driven instead of widget-heavy.
• Use separate Projects for truly unrelated work to reduce dataset size per Project.

Summary

Performance improves most from view simplification, Save View standards, and adequate device and network baselines.