...
Description
Sometimes you may need an automated way to export Jira issue information for use by an external application. For OnDemand users, this provides an option to get data out of Jira for other applications.
Links
See https://answers.atlassian.com/questions/84144/how-to-export-issues-as-a-csv-file/167654
Steps - simple case
Use the getIssueList action with the most appropriate outputFormat for your needs. JQL can be used or a filter can be used to select issues
Steps - large number of issues
Jira limits the number of issues that can be retrieved via JQL (default is 1000) although this can be customized for Jira download. There are 2 ways to deal with this.
Method 1:
- Construct your JQL to select subsets of data by project or issue type or similar so that each request is less than the limit.
- Depending on how you construct the JQL subsets, you may be able to use either the runFromProjectList, runFromList, or run actions.
- Run the getIssueList action multiple times with the append parameter to append data to the same file.
Method 2:
- Create a filter that matches your needs. For example, it is easy to create a filter for any JQL search.
- Make the filter a favorite filter for the user id that will run the automation. A favorite filter is required for #3 .
- Use the getIssueList action and specify the search filter. This method pages the results so that Jira retrieves less than the limit each time.
Info | ||
---|---|---|
| ||
This can take a while to process depending on the number of issues. Make sure your Java memory parameters are large enough to handle the amount of data as all data is in memory before being written to a file. |