Incidents

Incidents are a special type of requirement that indicates an issue with another requirement.

When to create an incident

Incidents should be created in the following situations:

Implementation Issues

1. Non-Compliance: When an implementation does not meet the specified requirement
2. Partial Implementation: When only part of a requirement has been implemented
3. Regression: When a previously working feature no longer functions correctly
4. Performance Issues: When the implementation meets functional requirements but fails performance criteria

Test Failures

1. Failed Verification: When a test case fails to verify a requirement
2. Blocked Testing: When testing cannot proceed due to environmental or prerequisite issues
3. Unexpected Behavior: When the system behaves differently than specified, even if technically passing a test

Process Issues

1. Missing Traceability: When requirements lack proper links to related items
2. Documentation Gaps: When supporting documentation is missing or inadequate
3. Review Findings: When issues are identified during formal reviews

How to create an incident

Creating an incident in Requify is straightforward:

From the Incidents Section

1. Navigate to the "Incidents" section in your project
2. Click "New Incident" in the top-right corner
3. Fill in the incident details:
   • Title: A clear, concise description of the issue
   • Description: Detailed explanation of the problem
   • State: Current state of the incident
   • Related Requirements: Link to affected requirements
   • Related Tests: Link to relevant test cases
   • Evidence: Attach screenshots, logs, or other supporting files
4. Click "Create Incident" to save

From a Requirement

1. Open the requirement with the issue
2. Click "Create Incident" in the actions menu
3. The incident form will open with the requirement pre-linked
4. Complete the remaining fields as described above

From a Test Case

1. During test execution, if a test fails
2. Click "Create Incident" on the test result page
3. The incident form will open with the test and its linked requirement pre-linked
4. Complete the remaining fields as described above

Incident Lifecycle

State Tracking

Incidents in Requify can have the following states:

• Draft
• Reported
• Not An Issue
• Working As Expected
• Low Priority
• Medium Priority
• High Priority
• Pending Review
• Fixed
• Verified
• Rejected

Assignment and Ownership

1. Assigning Incidents: Assign incidents to team members responsible for resolution
2. Ownership Transfer: Transfer ownership as the incident moves through different phases
3. Notifications: Team members receive alerts when incidents are assigned to them

Resolution Process

1. Analysis: Investigate the root cause of the incident
2. Planning: Determine the approach to resolve the issue
3. Implementation: Make the necessary changes to resolve the incident
4. Verification: Test the changes to ensure the incident is properly resolved
5. Documentation: Update requirements or other documentation as needed
6. Closure: Formally close the incident with resolution notes

Related to test cases

Incidents and test cases are closely integrated in Requify:

Creating Incidents from Test Failures

When a test fails:

1. The tester can immediately create an incident from the test result page
2. The incident is automatically linked to:
   • The failed test case
   • The requirement being verified
   • The test run
3. Test evidence (screenshots, logs) can be automatically attached to the incident

Test Case Updates

When an incident is resolved:

1. Related test cases may need to be updated to reflect changes
2. New test cases may be created to verify the fix
3. Regression tests should be added to prevent recurrence

Verification Testing

To verify that an incident has been resolved:

1. Create a verification test run targeting the specific incident
2. Execute the test cases linked to the incident
3. If all tests pass, the incident can be marked as "Verified"
4. If any tests fail, the incident remains "In Progress" or returns to that state