> For the complete documentation index, see [llms.txt](https://manual-v2.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual-v2.firstresonance.io/quality/create-issues.md).

# Create Issues

Create Issues at a moments notice, from anywhere within the application.

### Overview

Creating issues quickly ensures that problems are documented and routed to the right people without slowing down production. From anywhere in ION, a simple keyboard shortcut (Command-Shift-I) (Command-K) on Macs and (Control-Shift-I)(Control-K) on PCs opens the issue form or command menu where you can create issues. Users can add details such as the run and step where the issue occurred, related parts, descriptions of the problem, and the expected condition. This keeps critical context tied to the issue from the start.

Once captured, issues can be assigned to specific users and routed to the appropriate teams or locations. Required fields or attributes specific to the organization can also be filled in to support faster review and resolution. By standardizing how issues are logged, teams ensure that problems are well-defined, actionable, and resolved quickly, reducing downtime and maintaining quality.

### Creating an Issue in ION

#### Key Steps

**Step 1: Open Create New Issue Form** [0:00](https://loom.com/share/5add1d772eb14fc5a413e8b771ab927c?t=0)

![](https://loom.com/i/a7cf1a8249f444d496c619a48c765f54?workflows_screenshot=true)

* Press **Command-Shift-I** from anywhere within ION to open the Create New Issue form.
* Input the necessary information regarding the issue.

**Step 2: Select Run and Step (if applicable)** [0:34](https://loom.com/share/5add1d772eb14fc5a413e8b771ab927c?t=34)

![](https://loom.com/i/75ad50a3214a4719ad89f2dea11ed87a?workflows_screenshot=true)

* If the issue was found during a specific Run Step, select the appropriate **Run** and **Step** where the issue occurred.
* Note: This step is not mandatory.

**Step 3: Describe the Issue** [0:54](https://loom.com/share/5add1d772eb14fc5a413e8b771ab927c?t=54)

![](https://loom.com/i/0d60aa6f59f943e58b8a4ceec32743b3?workflows_screenshot=true)

* Select the parts related to the issue.
* Provide a description of why the issue is being captured.
* Include the expected condition for clarity.

**Step 4: Assign and Route the Issue** [1:27](https://loom.com/share/5add1d772eb14fc5a413e8b771ab927c?t=87)

![](https://loom.com/i/9a0f4bdb8d4643449a245706312c16b0?workflows_screenshot=true)

* Assign the issue to the appropriate locations.
* Designate a user responsible for addressing the issue.

**Step 5: Fill Out Required Attributes** [1:45](https://loom.com/share/5add1d772eb14fc5a413e8b771ab927c?t=105)

![](https://loom.com/i/a583a02b64ad47a487ddc8966dc3f1c4?workflows_screenshot=true)

* If your organization has specific attributes that need to be filled out, complete them in this section.
* Review all information to ensure completeness for quick resolution.
* Double-check the assigned user and locations to ensure proper routing of the issue or take advantage of ION's automated routing systems in the ION Marketplace.

#### Tips for Efficiency

* Familiarize yourself with the keyboard shortcuts (Command-Shift-I)(Control-Shift-I) to quickly access the issue creation form.

#### Link to Loom

<https://loom.com/share/5add1d772eb14fc5a413e8b771ab927c>


---

# 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://manual-v2.firstresonance.io/quality/create-issues.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.