Workfront Global Search should return matches across the full dataset (not limited to the first 2,000 results / page)

In large Workfront instances, Global Search / Advanced Search becomes inefficient because results are displayed in pages capped to a fixed batch size (e.g., 2,000 items per page). When an organization has thousands of objects (Projects, Documents, Users, Templates, etc.), searching for something specific may not appear on the first page—forcing users to manually click through multiple pages to find a known item. This creates friction for everyday navigation and slows down work, especially for admins and power users who need to locate records quickly. Workfront search is meant to help users “easily locate items” across many object types, but the current paging behavior undermines that goal at enterprise scale.

Why this feature is important

• Time savings & adoption: Users lose minutes per search when they must page through thousands of results, which hurts adoption and confidence in Workfront as the “source of truth.”
• Enterprise-scale usability: Many customers have 8,000+ projects/documents/users, and the search experience should scale accordingly.
• Reduces errors: Manual paging increases the risk of selecting the wrong object or assuming something “doesn’t exist” because it wasn’t in the first result set.
• Search is core navigation: Since search behavior already varies by permissions, missing items due to paging limits adds another avoidable obstacle.

How I would like the feature to work

Option A (Preferred – best UX): “Search first, then limit.”
When a user enters a search term, Workfront should query the entire searchable index for that object type and return the most relevant matches even if they would have been beyond the first 2,000 items in the underlying list. In other words: apply the search filter to the full dataset first, then display results.

Option B: “Show all results / larger page size.”
Add a user option (or admin-controlled setting) to increase “results per page” (e.g., 2,000 / 5,000 / 10,000) or provide a “Show all matches” mode for searches.

Option C: “Find within results across all pages.”
If Workfront must keep paging for performance, add a “Search within results” that searches across all pages and jumps directly to the matching items—without the user clicking Next/Next/Next.

(Any of the above would dramatically improve navigation for large environments.

Current behavior

When searching objects (Projects, Documents, Users, etc.), the results are shown in batches (example: 2,000 per page). If the item I need is in page 2/3/4, I must manually navigate across pages to find it. This is especially painful when I already know the name/ID and just need Workfront to take me to the correct object quickly.

Acceptance criteria (what “done” looks like)

1. A search term returns results from the full dataset for the selected object type, not just the first batch.
2. Exact matches (or strongly relevant matches) appear in the results even if the object would otherwise be beyond the first page.
3. Users can locate a known object without manually paging through results.
4. Performance is maintained (e.g., via indexing/relevance ranking), but completeness of matching is preserved.