...
Requirements: Specify the requirements for which the report needs to be generated. One or more requirement(s) can be specified via three options (requirements from multiple projects if linked with cases of the project can be specified)
List: search list of Jira issues via key or title. Users can filter the list by project name & Jira issue type
JQL (Jira Query Language): specify requirements meeting a criteria using standard JQL. Clicking on the JQL box opens up the standard Jira box which helps in faster JQL creation
Filter: select a filter created and saved in Jira (the list of filters from Jira is pre-populated and is shown upon clicking inside of the search box)
Include Child Issues:Selecting this checkbox will include the child issues of all the specified requirements. E.g. if the specified requirement is an Epic with multiple stories, all the stories don’t need to be specified separately if this option is checked. If not selected, only the parent issues are displayed in the report
Filter Child issues: Clicking the icon will allow users to specify which issue types to include in the report (e.g. user might only want to see stories not task/sub-tasks so in the dropdown user can select Story)
Cycles: Specify which execution cycles should be considered for traceability of the selected requirements; multiple cycles can be specified. If all or any of the check boxes under Cycles are selected, cycles list will need to be provided
Retrieve Runs: Check this box to see the test execution results in the traceability report. If not selected, execution details will not be displayed in the report
Retrieve Defects: Check this box to see the test execution defects in the traceability report. If not selected, defect details will not be displayed in the report
Include only last Run: Check this box if only the last run of the cases should be considered for the report. If not selected, all runs of the resulting cases will be shown in the report
...