Issues Rules
Issues serve as the foundation for governance traceability in software teams. These rules ensure every issue is well-defined, categorized, and linked to development activity.
| ID | Title | Description | Significance | Severity |
|---|---|---|---|---|
| I1 | Issue Title Convention | Issue titles must be concise yet descriptive | Best practise | medium |
| I2 | Minimum Assignees Required | Issues must have at least one assigned team member | Workflow Hygiene | medium |
| I3 | Issue Description Required | Issues must include a clear and detailed description | SOC-2 (Audit Readiness) | high |
| I4 | Required Issue Labels | Issues must be properly categorised with labels | Best practise | medium |
| I5 | Issue Assignee Time Limit | Issues must be assigned within 24 hours of creation | Workflow Hygiene | low |
| I6 | Issue Priority Label Required | Issues must include a priority label (e.g., P1, P2, P3) | Incident Management Policy | medium |
| I7 | No Duplicate Issues | New issues must not duplicate existing open issues | Quality Control | high |
| I8 | Assigned Before Closing | Issues must be assigned to a user before they are closed | SOC-2 (Ownership Traceability) | medium |
| I9 | Must Reference Related PR | Issues must reference a related PR or indicate blocked status | SDLC Compliance | medium |
| I10 | Response Time SLAs | Issues must receive a first response within 48 hours of creation | SLA Enforcement / SOC-2 CC6.1/C7.2 | low |
💡 Want to recommend a rule? Contact us at support@warestack.com — we’d love to hear from you.
Last updated on