Currently, updating requirements fields via import from an Excel file requires that the import file contains the Name of the requirement - but what if the Name is not unique, or the Name is not available? Why isn't the ID enough?
Background: We want to integrate requirements work with testing, where the testers manage their test cases in a tool other than CaseComplete (not negotiable).
when mapping Test Cases to requirements, we could to enter the requirement ID into the other tool
we would like to import information from the other tool to CaseComplete, such as test coverage and test outcome. To do so, the other tool could create an Excel file that has the requirement ID, test case ID, and test outcome ... but CaseComplete won't import this, unless we also have the (potentially non-unique) Name of the requirement
Please sign in to leave a comment.
Hi, and thanks for the suggestion. We will certainly take it under advisement - it makes sense - and look at implementing your suggestion in future releases of CaseComplete.
One item of note: while a name field is currently required in an Excel import, it does not have to be a unique name at this time. As long as IDs are used, the import will still get mapped properly.
