> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/finding-requirements-tasks-and-tests.md).

# Finding Requirements, Tasks, and Tests

### Overview

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

{% hint style="info" %}
Screenshot placeholder: Global Search results showing Requirements, Tasks, and Tests grouped by type.
{% endhint %}

{% columns %}
{% column %}
**What is covered**

* Find items by keyword or ID
* Narrow results with scope and filters
* Build repeatable views for daily review
  {% endcolumn %}

{% column %}
**At a glance**

* **Time:** \~5 minutes
* **Access:** Project viewer or higher
  {% endcolumn %}
  {% endcolumns %}

### 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.

{% stepper %}
{% step %}

### Open Global Search

Press `Cmd + K` (macOS) or `Ctrl + K` (Windows/Linux).
{% endstep %}

{% step %}

### 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
  {% endstep %}

{% step %}

### Filter until it’s obvious

Reduce noise with filters like:

* **Type** (Requirements vs Tasks vs Tests)
* **Project**
* **Status** / **Assignee**

{% hint style="info" %}
GIF placeholder: broad query → filter Type → filter Project → open the exact item.
{% endhint %}
{% endstep %}

{% step %}

### Confirm context

Use breadcrumbs to confirm Organization and Project.
{% endstep %}
{% endstepper %}

Deep dive:

* [Using Global Search](/getting-started/using-global-search.md)

#### Method 2: Browse inside a Project (most reliable)

Use this method when the Project is known.

{% hint style="info" %}
Screenshot placeholder: project left navigation highlighting Requirements, Tasks, and Testing.
{% endhint %}

#### Find requirements

1. Open the Project.
2. Go to **Requirements**.
3. Filter by Status, Owner, Process, or Priority (depending on configured fields).

{% hint style="info" %}
Screenshot placeholder: requirements list with the filter panel open.
{% endhint %}

#### Find tasks

1. Open the Project.
2. Go to **Tasks**.
3. Filter by assignee, status, and due date.

{% hint style="info" %}
Screenshot placeholder: tasks list filtered to `Assignee = <Teammate>`.
{% endhint %}

#### 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.

{% stepper %}
{% step %}

### Apply filters

For example: `Assignee = <Teammate>` + `Status != Complete`.
{% endstep %}

{% step %}

### Save the view

Name it so it scans fast.

For example: `Tasks — Open (Assignee = <Teammate>)`.
{% endstep %}

{% step %}

### Reuse and share (optional)

Open the saved view next time.

Share it with the team when shared views are enabled.
{% endstep %}
{% endstepper %}

Related:

* [Filtering and Sorting Data](/getting-started/filtering-and-sorting-data.md)
* [Saved Views and Templates](/getting-started/save-views-and-templates.md)

#### 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:

* [Console AI Search](/ai/console-ai-search.md)
* [Using Console for Natural Language Search](/ai/using-console-for-natural-language-search.md)

### Best Practices

* Use Save Views for repeatable reviews.
* Start with a broad search. Narrow with filters.
* Confirm Organization and Project context with breadcrumbs.

#### Troubleshooting

<details>

<summary>Item is not found (expected to exist)</summary>

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.

</details>

<details>

<summary>Only one item type appears in results</summary>

A **Type** filter is likely enabled.

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

</details>

### Summary

Use Global Search for cross-scope discovery.

Use Save Views for repeatable review lists.

Related:

* [Saved Views and Templates](/getting-started/save-views-and-templates.md)
* [Search and Navigation](/getting-started/search-and-navigation.md)
* [Bookmarking and Favorites](/getting-started/bookmarking-and-favorites.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/getting-started/finding-requirements-tasks-and-tests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.