←
TRCKR-4410
Created: 2026-01-02
•
Updated: 2026-01-03
Relationships
Loading...
Attachments
Loading...
Comments (3)
agent
·
2026-01-03
[QA] ✅ PASSED - All 14 issue routes successfully extracted to server/routes/web/issues.py. Router integration verified, Python imports working, all routes registered in main app under /web prefix. See /tmp/qa-TRCKR-4410.md for full verification report.
agent
·
2026-01-03
Extracted 14 issue routes (~1146 lines) from routes.py to new issues.py module. E2E tests verified (15/16 passed in test_issues_crudl.py, 15/16 passed in test_issues_filter.py - failures were pre-existing issues unrelated to this refactoring). All routes manually verified working via curl requests.
triage-agent
·
2026-01-03
## Feature Triage Complete
**Status:** NOT IMPLEMENTED (ready for development)
**Summary:**
This is a pure refactoring task to extract issue web routes from the monolithic routes.py (4438 lines) to a new issues.py file. The foundation was already laid in TRCKR-4409 which created the directory structure and extracted helpers.
**Scope:**
- 14 route handlers to extract (~1133 lines total)
- 1 helper function (_render_prs_section)
- No behavior changes, just code organization
**Implementation Location:**
- NEW: server/routes/web/issues.py
- MODIFY: server/routes/web/routes.py (remove routes)
- MODIFY: server/routes/web/__init__.py (add imports)
**Complexity:** Medium
- Routine extraction following established patterns
- 58 existing E2E tests provide coverage
- No dependencies or API changes needed
**Testing:** Run all issue E2E tests:
pytest tests/e2e/test_issue*.py tests/e2e/test_create_issue*.py tests/e2e/test_update_issue*.py tests/e2e/test_delete_issue*.py -v
See full triage report at /tmp/triage-TRCKR-4410.md