- User's guide
- Projects' organization
- Test design
- Organizing tests
- Test planning
- Test execution
- Reporting and tracking
- Import/Export TCT
- Export test issues
- Issue search dialog
- TestFLO menu
- Admin's guide
- Project configuration
- Test Automation configuration
- TestFLO settings
- TestFLO Permissions
- Custom fields
- Advanced workflow configuration
- Panel Filter Result
- Upgrade reports
- Upgrade guide
The Requirements module gives you the opportunity to define from which project and which issue types should be considered as requirments in source project. There can be several issue types in this category, even subtasks. It can be Story, Epic, New Feature or any other revelant issue type. The selected pairs have an impact on limiting the selection of requirements when using the Link requirement operation and in the Requirement field.
Requirements module requires Test Repository or Test Execution module enabled to allow configuration.
To select issue type as requirement
Click Add project.
Click Select and choose project for storing requirements.
Click Select and choose issue type which will be used for defining requirements.
The defined requirements have been saved. If you need, it is possible to add more projects and issue types. Just repeat the steps above.
Selected project and issue types pairs are automatically created as restriction for Requirement custom field (Enhanced Issue Picker CF type). It also affects the Link with Requirement operation on all test objects.
We do not recommend manually changing the restrictions in the Requirement custom field. All changes had to be made only in the Requirements tab.