- We import requirements in files attached to pages,
- The Excel file must remain attached to the page,
- When someone updates the file, the requirements are updated. If the columns are different, we skip this importation.
- When someone removes the file, the requirements are removed.
- It supports importing the key, the description, and the properties.
- Requirements in pages can mention a requirements of an Excel file, but it's not possible to put dependencies in Excel files.
- Baselines are not available for Excel requirements, for the moment.
Uploading an Excel document
There is a new tab in the Requirement Yogi screen:
New uploads must be attached to a page.
The file is uploaded. Map the columns.
What about dependencies?
- It is possible to link to an Excel requirement,
- But it is not possible to mention other requirements in Excel spreadsheets.
- When clicking on an Excel requirements, it leads to the import page, with the row highlighted in yellow:
Note that the last uploaded file is displayed, although it may not be successfully imported. If the data doesn't match, check the column mapping and hit "Import" again.
The Excel import applies the "Import limit" from the Global limit. The default is 2000 requirements.
"Big" files can lead to an out-of-memory error:
- If you wish to disable the Excel import on a single file, remove the "ry-excel-import" label. Requirements from this spreadsheet will be marked as deleted.
- If you wish to disable the Excel import on the whole instance, use the system property -Dplaysql.disable.excel.import=true
- If you wish to limit the number of requirements, change the Global limit,
- It is not possible to limit the file size, because we've noticed that file size wasn't an accurate indicator of the number of rows and columns in a file.
We've mentioned this advice on the Release Notes 2.0.