- Basic concepts
- Quick guide for Jira Administrator
- Quick guide for QA manager
- Quick guide for testers
- Demo environment
- Reporting & tracking
- Reporting and tracking overview
- Requirement Test Coverage Report
- Requirement Traceability Report
- Requirement Test Execution Report
- Test Plan Execution Report
- Test Plan Iterations Report
- Test Execution Report
- Test information panel
- Issue panels
- Export test issues
- Dashboard Gadgets
- Administration & Configuration
- Projects' organization
- Create project
- Project configuration
- TestFLO settings
- TestFLO Permissions
- Custom fields
- Advanced workflow configuration
- Panel Filter Result
- Import/Export TCT
- Test Automation configuration
- 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 Select below the Project option and select a project from which you want to define requirements.
Click Select below the Issue types option and select the issue type/s 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.