The Document Generator feature is available on:
You can create documents directly from the Issue detail screen by clicking on Xray Document Generator button available on tools section.
After clicking on it, a dialog is shown with the following fields:
Templates are grouped by global and project templates. Each template has its own output formats pre-defined.
Once you have selected the template, you have to select the desired output format.
Having choose the template and the output format, now you can generate your document by clicking on Export button, otherwise, we can close the dialog by clicking on Close button.
Once the generation process is finished you can get your document by clicking on Download button. If you want to generate another document you just have to click on Back button or leave the dialog by closing it.
You can create documents directly from the Issue Navigator screen by clicking on the Xray Document Generator button available on tools sections as shown in the image below.
Regarding the template selection and the output format is exactly the same as explained above on Single issue details. There is only one diference here, the Break Type, where you can define if you want or not a page break on word documents.
The values available for this field, are:
Break Type | Expected behaviour |
---|---|
Components | If the component is different from the previous issue processed, then a new page break will be added. |
Issues | A page break is added for each issue processed. |
Issue Types | If the issue type is different from the previous issue processed, then a new page break will be added. |
Project | If the project is different from the previous issue processed, then a new page break will be added. |
Never | No page break will be added. |
The Export process is exactly the same as mentioned above, so you just have to click on Export and when it's finished, click on Download to get the document.
You can export information through the Test Plan Board has the following:
You can export all information about the tests that are inside the selected folder and you can choose to include or not the tests from the inner folders.
You can export info regarding the selected tests you have chosen at the Test Plan test list.
This button allows you to export all the Test Plan info of the selected test plan. For example, all the test status exported will be directly related to the selected test plan.
At the test repository board, you can also export information about tests that are included in the folders or at the test list, the same as the test plan board.
Whenever there's an issue or project for Xray available in an agile board, Document Generator is available to export.
It allows selecting all the available issues or a subcontext of Scrum and Kanban boards (Backlog, Releases, and Active Sprint pages).
You can export all Xray issues from the Kanban Backlog Page by clicking on our button through the Board options list.
The same process can be done through the Kanban Active Board Page.
At the Releases page, we can export information about a Release selecting at the right side the release we want to export, as we can see in the following example:
When you select a release to see its details, you have a Document Generator button ready to export information regarding the selected release.
You can export all Xray issues from the Scrum Backlog page by clicking on our button through the Board options list.
The same process can be done through the Scrum Active Board Page.
At the Releases page, we can export information about a Release selecting at the right side the release we want to export, as we can see in the following example:
When you select a release to see its details, you have a Document Generator button ready to export information regarding the selected release.
The Maximum number of issues that can be Exported using the Document Generator can be set on the Max number of issues that can be exported entry in Xray settings.
The default is 1000, but the value can be adjusted between 1 and 10000.
Exporting high number of issues at the same time may affect the performance of your Jira instance.