> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/quality-managers/incident-application/tracking-and-monitoring-incidents/my-submitted-incidents.md).

# My Submitted Incidents

Track the incidents you've submitted.

Use the **My Submitted Incidents** module to view and monitor all incidents you have submitted, whether open, under investigation, or closed.

{% hint style="info" %}
“My” refers to the currently logged-in user. You are the creator and owner for the incident reports listed.
{% endhint %}

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

## Viewing Incidents

Follow the steps below to locate and review incidents efficiently.

{% stepper %}
{% step %}

### Filtering Incidents

Use the **filter row** below the column headers to find specific incidents or narrow the results displayed in the grid.

Commonly used filters include:

* **Status:** Filter incidents by their current stage in the workflow.
* **Incident ID:** Filter incidents by unique identifier.
* **Incident Name:** Filter incidents by keywords in the title.
* **Severity:** Filter incidents by their severity level.
* **Priority:** Filter incidents by their priority level.
* **Occurred:** Filter incidents by the date and time they occurred.
* **Reported:** Filter incidents by the date and time they were reported.

{% hint style="success" icon="lightbulb" %}

#### Tips for Filtering

Filtering options vary depending on the column’s data type.

* **Text Search:** Type directly in the filter field to quickly find matching values.
* **Dropdown:** Select a value from the dropdown (e.g., true or false).
* **Advanced Filtering:** Use the **magnifying glass** ( <i class="fa-magnifying-glass">:magnifying-glass:</i> ) icon to apply conditions (e.g., equals, contains, or range-based filters).
* **Date/Time Filtering:** Use the **calendar** ( <i class="fa-calendar">:calendar:</i> ) icon to select specific values.

If the filter field is not editable or no controls are available, the column cannot be filtered.
{% endhint %}

***

{% endstep %}

{% step %}

### Accessing Incidents

To open a specific incident report, click the **View** ( ![](https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIAlpvjgSBR3lKZjwsXm7%2FIMS-KI-L-9.svg?alt=media\&token=262f3701-b544-43fe-b1bc-d17a29a18e55) ) icon next to it.

* The report opens in read-only mode, where you can:
  * Review all details
  * [View or download attached templates](/interfacing-help-files/end-users/exploring-apps/working-with-forms/generating-templates.md)

{% hint style="success" icon="lightbulb" %}
**Tip:** Check the **Status** column in the grid to see the report's current stage in the [**Incident Management**](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents.md) workflow.
{% endhint %}

***

{% endstep %}
{% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>How to Export Grid Data</strong></td><td>Export grid contents to an Excel file.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2F8EURtbR8olEYsY7knlFB%2FIMS-V16-NAV-Library-Icons-106.png?alt=media&amp;token=7664c54c-4826-48e4-8ca0-d042582c2f2d">IMS-V16-NAV-Library-Icons-106.png</a></td><td><a href="/interfacing-help-files/end-users/exploring-apps/working-with-forms/working-with-grids.md#exporting-data-to-excel">Working with Grids</a></td></tr></tbody></table>


---

# 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://interfacing.gitbook.io/interfacing-help-files/quality-managers/incident-application/tracking-and-monitoring-incidents/my-submitted-incidents.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.