PUT /rest/api/2/issues/archive/export
Enables admins to retrieve details of all archived issues. Upon a successful request, the admin who submitted it will receive an email with a link to download a CSV file with the issue details.
Note that this API only exports the values of system fields and archival-specific fields (ArchivedBy
and ArchivedDate
). Custom fields aren't supported.
Permissions required: Jira admin or site admin: global permission
License required: Premium or Enterprise
Signed-in users only: This API can't be accessed anonymously.
Rate limiting: Only a single request can be active at any given time.
Servers
- https://your-domain.atlassian.net
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
projects[] |
Array | No |
List archived issues with a specified project key. |
reporters[] |
Array | No |
List archived issues where the reporter is a specified account ID. |
archivedBy[] |
Array | No |
List archived issues archived by a specified account ID. |
issueTypes[] |
Array | No |
List archived issues with a specified issue type ID. |
archivedDateRange |
Object | No |
List issues archived within a specified date range. |
archivedDateRange.dateBefore |
String | Yes |
List issues archived before a specified date provided in the YYYY-MM-DD format. |
archivedDateRange.dateAfter |
String | Yes |
List issues archived after a specified date, passed in the YYYY-MM-DD format. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.