Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Finding Requirements, Tasks, and Tests

Locate work items using Global Search, project navigation, filters, and saved views.

Overview

Use this workflow to locate a specific item or build a clean list. The same patterns apply to Requirements, Tasks, and Tests.

Screenshot placeholder: Global Search results showing Requirements, Tasks, and Tests grouped by type.

What is covered

  • Find items by keyword or ID

  • Narrow results with scope and filters

  • Build repeatable views for daily review

At a glance

  • Time: ~5 minutes

  • Access: Project viewer or higher

Key Concepts

  • Global Search: cross-scope search for items

  • Project navigation: reliable browsing when Project is known

  • Save View: stored view configuration for repeatable lists

How It’s Used

Use Global Search to locate items by keyword or ID. Use Save Views for daily review lists.

Benefits

  • Faster retrieval of single items

  • Repeatable lists for triage and review

Setup Steps

Method 1: Global Search (fastest)

Global Search is best when item location is unknown.

1

Open Global Search

Press Cmd + K (macOS) or Ctrl + K (Windows/Linux).

2

Search using known context

Try:

  • a unique keyword from the title or description

  • an ID like REQ-042 or TASK-015 (if IDs are enabled)

  • a Teammate name to find assigned work

3

Filter until it’s obvious

Reduce noise with filters like:

  • Type (Requirements vs Tasks vs Tests)

  • Project

  • Status / Assignee

GIF placeholder: broad query → filter Type → filter Project → open the exact item.

4

Confirm context

Use breadcrumbs to confirm Organization and Project.

Deep dive:

Method 2: Browse inside a Project (most reliable)

Use this method when the Project is known.

Screenshot placeholder: project left navigation highlighting Requirements, Tasks, and Testing.

Find requirements

  1. Open the Project.

  2. Go to Requirements.

  3. Filter by Status, Owner, Process, or Priority (depending on configured fields).

Screenshot placeholder: requirements list with the filter panel open.

Find tasks

  1. Open the Project.

  2. Go to Tasks.

  3. Filter by assignee, status, and due date.

Screenshot placeholder: tasks list filtered to Assignee = <Teammate>.

Find tests

  1. Open the Project.

  2. Go to Testing or Tests.

  3. Filter by phase, owner, and execution status.

Method 3: Filters + Save View (repeatable lists)

Use a Save View for work checked daily.

1

Apply filters

For example: Assignee = <Teammate> + Status != Complete.

2

Save the view

Name it so it scans fast.

For example: Tasks — Open (Assignee = <Teammate>).

3

Reuse and share (optional)

Open the saved view next time.

Share it with the team when shared views are enabled.

Related:

Method 4: Console search (natural language)

Use Console to get an answer, not a list.

For example:

  • show blocked requirements in finance

  • what tasks are overdue this week

  • tests that failed in UAT

Related:

Best Practices

  • Use Save Views for repeatable reviews.

  • Start with a broad search. Narrow with filters.

  • Confirm Organization and Project context with breadcrumbs.

Troubleshooting

Item is not found (expected to exist)

Check these in order:

  1. Clear filters. Then search again.

  2. Confirm the correct Organization and Project are selected.

  3. Try a shorter keyword.

  4. Confirm permission exists to view the item.

Only one item type appears in results

A Type filter is likely enabled.

Clear the type filter. Then re-run the search.

Summary

Use Global Search for cross-scope discovery.

Use Save Views for repeatable review lists.

Related:

Last updated