A new documentation is available for Squash TM 2.0 and later versions, check it here

3.06 - Export requirement(s)

3.6.1 Export from the tree structure

Squash TM enables you to export requirements in .xls format. Default file name is "export-requirements_yyyymmdd_hhmmss" (The date format depends on the language of your web browser).

Exported data are data linked to selected requirements. Simple or multiple selection can be performed on different requirements, sub-folders, folders and/or projects. Requirements are exported from the selected tree structure level (project, folder or sub-folder). Squash follows the path of the selected requirements in the tree structure.

Prerequisite: A project is created, and contains requirement(s) (including folders and sub-folders).

Select the requirement or the wanted branch in the tree structure, then click on [Import/Export] (seen here). Click on [Export…] in the drop down menu:

2. A pop-up window "Export" opens up. This pop-up enables you to rename the export file and to confirm or cancel the operation by clicking on [Cancel] or [X].

3. Click on [Export]. The.xls file is generated and the pop-up shuts itself. The export file can be downloaded.

FOCUS

It is possible to export the type fields "rich text" with their HTML tags (to preserve the formatting in a future import) by checking the box "Keep rich text format".

4. Generated export file contains two tabs:

1. 1. - REQUIREMENT: contains data related to the requirements (e.g. Description, Status, etc.). One row corresponds to one requirement.
    - LINK_REQ_TC: contains information to link a test case to requirements. This tab contains three columns :
      - REQ_PATH: requirement path (in the tree structure) from the project name to the requirement name (current version) NB: current version name can be different from the version name to link.
      - REQ_VERSION_NUM: requirement version number.
      - TC_PATH: test case path (in the tree structure) from the project to the test case name.
    - LINK_REQ_REQ: contains information to link the requirement versions together. This tab contains five columns:
      - REQ_PATH: requirement path (in the tree structure) from the project name to the requirement name (current version) NB: current version name can be different from the version name to link
      - REQ_VERSION_NUM: requirement version number.
      - RELATED_REQ_PATH: linked requirement path (in the tree structure) from project name until requirement name (current version) NB: current version name can be different from the version to link
      - RELATED_REQ_VERSION_NUM: linked requirement version number
      - RELATED_REQ_ROLE: linked requirement role code

3.6.2 Export a requirement from search results

It is possible to export a requirement from the "Search criteria for requirements" page.

In the requirements workspace, above the tree stucture, click on
On the "search criteria for requirements" page, select one or many projects where requirements are to be exported.
Fill in the criteria and click on [Search].
The search results page shows up.

5. Select one or several requirements to be exported and click on [Export] on the right.

6. The export file is the same as the one in "Export from the tree structure" section.

Page updated

Report abuse