> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/inbox/issues-list.md).

# Issues List

The Issues List consolidates crashes, app hangs, force restarts, bug reports, AI-detected issues, and performance metrics into one ranked view of your app.

***

### What Is the Issues List?

The Issues List is a centralized view that consolidates all your app's stability and performance issues into a single list. By combining issues like crashes, app hangs, force restarts, Bug Reporting items (both single bugs and **Bug Grouping** parents), AI-detected issues from [**Detect Agent**](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/detect-agent.md) (visual issues and broken functionality), and performance metrics like app launches and screen loads, it provides a comprehensive understanding of the problems affecting your app’s quality.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-9390fcc4542a5fb2610fc7f1c0168c17f9146d51%2Fproduct-guides-issues-list-1-1cb74c3d.png?alt=media" alt="The Issues List showing a crash, a network call and a flow, each with its frustration impact, issue count and team"><figcaption></figcaption></figure>

### How Does It Help?

The issues list is **automatically prioritized based on each issue's impact on your App Frustration-Free Sessions**, reflecting how much the issue contributes to frustrating user sessions. By addressing the highest-impact issues first, you can significantly improve your app's quality, reduce user frustration, and boost satisfaction.

Instead of sifting through raw data or dealing with scattered issues, you can now rely on this prioritized list to efficiently manage and resolve the most critical problems first.

***

### Using the Issues List: A Workflow for Improving App Stability and Performance

#### Step 1: Monitor Your App’s Frustration-Free Sessions

The **App Frustration-Free Sessions** is your most important metric for understanding your app’s overall stability and performance. It gives you a clear signal when users experience frustrating sessions, helping you take action before issues escalate.

If you want to improve your Frustration-Free Sessions, head to the **Issues List**, a prioritized view of every performance and stability issue contributing to the score. This leads us to step 2.

#### Step 2: Identify High-Impact Issues

After monitoring your Frustration-Free Sessions, drill down into the Issues List to pinpoint the most critical problems affecting your app. The list ranks issues by their [**Frustration Impact**](https://docs.luciq.ai/product-guides-and-integrations/product-guides/inbox/issues-list/frustration-impact.md), a metric that approximates how much each issue contributes to frustrating user sessions. This is calculated as:

`((Frustrating Sessions caused by this issue + 0.5 × Tolerable Sessions caused by this issue) ÷ Total Sessions) × 100`

Issues are grouped into the following categories:

* **High Impact:** Issues with a Frustration Impact of ≥0.5%. These are critical and require immediate attention.
* **Medium Impact:** Issues with a Frustration Impact between 0.01% and 0.5%. These should be addressed after high-impact issues.
* **Low Impact:** Issues with a Frustration Impact of <0.01%. These have minimal impact but may still need resolution over time.
* **No Impact:** Issues that don’t affect your Frustration-Free Sessions, including:
  * APM groups where all occurrences are satisfying (Apdex 1).
  * Metrics marked as non-key by your team.
  * Bug Reporting items, which are always added with **No Impact** so they don’t affect your Frustration-Free Sessions score. You’ll find them at the end of the Issues List, or by applying the **Bugs** filter. Grouped or duplicate bugs show a **count**, and clicking any bug row deep-links straight to that bug's detail page in Bug Reporting.
  * AI-detected issues from [**Detect Agent**](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/detect-agent.md), which are also added with **No Impact**. Each row's **Type** reads **Single**, or **Group** with the number of occurrences it holds, alongside when the issue was first and last seen. Clicking a row opens it on the AI Issues page.

For each issue, review:

* **Issue Count:** Represents the number of negative occurrences.
  * For crashes, app hangs, and force restarts: Total number of occurrences.
  * For APM metrics: Dissatisfying count, which is calculated as:\
    Frustrating Occurrences + (0.5 × Tolerable Occurrences)
* **Detailed Metrics:** Depending on the issue type, detailed metrics on the issue card provide insights into the issue’s scope and severity.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-f512c9b03808bf41d1761baa7f616c44c5593f8b%2Fproduct-guides-issues-list-2-44342164.png?alt=media" alt="The Inbox with the Frustration-Free Sessions score above the Issues List and the impact tooltip open on the top issue"><figcaption></figcaption></figure>

Now that you've identified the issues that are impacting your users the most, the next step is to take action and address them effectively.

#### Step 3: Triage the Issue

Review the prioritized issues to determine the appropriate next steps:

**Forward to Jira**

For critical issues requiring immediate attention, forward them to Jira for tracking and resolution.

* The generated Jira ticket includes relevant context about the issue.
* Once forwarded, a shortcut to the Jira ticket will appear on the issue card for quick access.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-c5dd4e3c23cbe1099d51d5e17124043b711635ee%2Fproduct-guides-issues-list-3-e561e524.png?alt=media" alt="The row menu open on an issue, with Forward issue listing Jira boards and a Linear integration"><figcaption></figcaption></figure>

**Assign to Teams**

* Assigning ensures accountability and streamlines communication.
* Assigned issues will be reflected in the team’s dashboard for full visibility.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-41ba5200a6133d9f9231bd351e823d84ea195146%2Fproduct-guides-issues-list-4-f63a0a0d.png?alt=media" alt="The row menu open on an issue, with the list of teams to assign it to"><figcaption></figcaption></figure>

**Triage Several Issues at Once**

When the same action fits many issues, you can apply it to all of them in one step instead of row by row.

* Use the checkbox at the start of each row to select issues.
* Use the checkbox in the list header to select every issue on the page. It shows a partial state when only some issues are selected.
* The header shows how many issues you selected, with the bulk actions next to it.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-9cb19e9332f5b8449f762fa204d0665dbecf1e88%2Finbox-bulk-actions-selected.png?alt=media" alt="The Issues List with an app hang, a force restart and a crash selected, and the Team and Forward bulk actions in the list header"><figcaption></figcaption></figure>

The bulk actions are:

* **Team**: assign one team to every selected issue, or choose **Unassigned** to remove the team. Available for crashes, bugs, network calls, flows, screen loading, and screen rendering. Screen loading and screen rendering ask you to confirm first, because changing their team also updates the ownership rules for related issues on the same screens.
* **Forward**: send every selected issue to one of your Jira or Linear integrations. Available for crashes and APM issues. When crashes are in your selection, the list only shows the integrations set up for Crash Reporting.
* **Mark as key metric** and **Ignore**: shown when your selection includes APM issues. They work the same way as on a single issue: **Ignore** unmarks the issues as key metrics, so they no longer count toward your Frustration-Free Sessions.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-08051bb8d59cde511e0963c270b892457e776ec6%2Finbox-bulk-actions-forward.png?alt=media" alt="The bulk Forward menu listing Jira and Linear integrations for the selected issues"><figcaption></figcaption></figure>

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-0807a2d6fda2fa79b19932bc0b3016d59f41ffb8%2Finbox-bulk-actions-ignore.png?alt=media" alt="The confirmation dialog for ignoring two selected issues"><figcaption></figcaption></figure>

An action only runs when it fits **every** selected issue. If it doesn't, it stays visible but grayed out. Hover over it to see why, for example **Not available for app launches**, or that your role doesn't allow it for one of the issue types you selected.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-8367b63eb70259808da8122f65c9bfc34da8b0f3%2Finbox-bulk-actions-disabled-reason.png?alt=media" alt="The Team bulk action grayed out with the tooltip Not available for app launches"><figcaption></figcaption></figure>

Once an action finishes, a message confirms it and the list updates. Your selection can mix issue types, such as crashes, bugs, and network calls. If the action fails for one of them, the message names it, and the issues of the other types are still updated.

{% hint style="info" %}
The checkboxes only appear if your role can change issues in at least one product. AI-detected issues from Detect Agent don't support bulk actions yet.
{% endhint %}

#### Step 4: Fix the Issue

When you’re ready to fix an issue, click on it in the Issues List or open it through the link in your Jira ticket. You’ll be redirected to the issue’s **Details Page**, where you’ll find all the debugging data you need to resolve the problem efficiently.

***

### Coming Back to the Same Slice of the List

If you work a particular slice of the Issues List regularly, say hangs and force restarts, or only the bug reports, you can save those filters and that sort order as a named view and return to it in one click. See [Saved Views](https://docs.luciq.ai/product-guides-and-integrations/product-guides/inbox/issues-list/saved-views).

***

### Related

* [Inbox](https://docs.luciq.ai/product-guides-and-integrations/product-guides/inbox.md): how the Issues List and Opportunities work together.
* [Opportunities](https://docs.luciq.ai/product-guides-and-integrations/product-guides/inbox/opportunities.md): what to build next, from your users' feedback.
* [App Health Dashboard](https://docs.luciq.ai/product-guides-and-integrations/product-guides/getting-started-with-luciq/app-health-dashboard.md): the overall quality picture the Issues List drills into.
* From your AI client: the `list_issues` and `ai_issue_details` tools in the [MCP Tools Reference](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server/mcp-tools-reference.md). From the terminal: `luciq issues list` in the [CLI Command Reference](https://docs.luciq.ai/product-guides-and-integrations/product-guides/luciq-cli/command-reference.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/inbox/issues-list.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
