> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/plugins/first-party-ango-plugins/issue-export.md).
# Issue Export
## Overview
The Issue Export plugin is an export plugin that downloads issue data from a project as CSV reports.
Use this plugin when you need to audit open and resolved issues, review issue status by task or creator, or analyze issue error types and error codes outside Ango Hub.
## Plugin Functionality
The Issue Export plugin creates a ZIP file containing multiple CSV files.
The export includes:
**\[Issue] File**
Contains one row per issue, including the issue ID, issue link, task, asset, stage, creator, status, class name, error type, error code, content, comments, and position or page information when available.
**\[Asset] File**
Aggregates issue counts by task and asset.
**\[Created By] File**
Aggregates issue counts by the user who created the issue.
**\[Created To] File**
Aggregates issue counts by assignee when assignee information is enabled and available.
**\[Overview] File**
Summarizes issue totals by status, error type, and error code.
## Plugin Configuration
From the **Stage Filter** field, pick the stages containing the tasks whose issues you'd like to export. Similarly, from the **Batch Filter** field, you may select one or more batches. By default, all tasks are exported from all batches.
If you wish to receive an email when the export is complete, toggle **Send Email** on.
You may vary a number of settings related to your export from the **Config JSON** field. Each option is detailed below:
```json
{
"mode": "default",
"add_assignee_info": true,
"logging_frequency": 0
}
```
* **"mode":** Defines the export mode. The default mode exports general Ango Hub issue reports.
* Example:
* "mode": "default"
* **"add\_assignee\_info":** When `true`, the plugin includes assignee-based issue reporting where the data is available.
* Example:
* "add\_assignee\_info": true
* "add\_assignee\_info": false
* **"logging\_frequency":** Defines how frequently progress logs are displayed; setting this value to 0 disables progress-frequency logging.
* Example:
* "logging\_frequency": 0
* "logging\_frequency": 100
---
# 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.imerit.net/plugins/first-party-ango-plugins/issue-export.md?ask=&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.
