> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/codescan/issues/exporting-issues-using-codescan-export-tool.md).

# Exporting Issues using CodeScan-Export Tool

This guide will walk you through the steps necessary to export a **.CSV** report of your project's issues.

#### Requirements <a href="#requirements" id="requirements"></a>

1. A Bash terminal (such as Git Bash)
2. The [codescan-export tool](https://www.npmjs.com/package/codescan-export) (This can be acquired through Node.JS or git)
3. Your CodeScan credentials:
   * [Organization Key](https://knowledgebase.autorabit.com/codescan/docs/finding-your-organization-keys)
   * [Project Key](https://knowledgebase.autorabit.com/codescan/docs/finding-your-project-key)
   * [Security Token](https://knowledgebase.autorabit.com/codescan/docs/generate-a-security-token)

The plug-in can be used by simply calling it from the CLI and feeding it with the required parameters.

Enter the following command to see a list of options.

```
codescan-export -h
```

**Example, usage of the plugin to pull all issues:**

{% code overflow="wrap" fullWidth="false" %}

```
codescan-export MyOrganizationKey MyProjectKey --token=MyToken -f C:/MyDirectory/MyFileName.csv
```

{% endcode %}

**Example, usage of the plugin to pull all issues with the severity of blocker or critical:**

{% code overflow="wrap" %}

```
codescan-export MyOrganizationKey MyProjectKey --token=MyToken --types=BUG --severities=BLOCKER,CRITICAL -f C:/MyDirectory/MyFileName.csv
```

{% endcode %}

**The following video will provide you with step-by-step instructions for exporting issues:**

{% file src="/files/elUpPGdfuCKqzrS8cA0d" %}


---

# 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://knowledgebase.autorabit.com/product-guides/codescan/issues/exporting-issues-using-codescan-export-tool.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.