This Issue Log Software Development document shows how Eduardo Montes tracked all six active issues of the ProjectAdm SaaS platform from identification through resolution — documenting each issue's impact, owner, resolution actions, and final status across 28 sprints. This Excel register is the operational heart of the ProjectAdm risk and issue management process, giving the team and steering committee a single source of truth for what was broken, who was fixing it, and when it would be resolved.

What Is an Issue Log?

An Issue Log is a PMBOK 8 output in the Uncertainty Performance Domain that records all project issues — problems that have already materialized and require active resolution, as distinct from risks (which are potential future problems). The Issue Log tracks each issue's ID, description, date identified, owner, priority, impact on scope/schedule/cost, resolution actions taken, target resolution date, and final resolution status. Maintaining an active issue log prevents issues from being forgotten, ensures ownership is assigned, and provides an audit trail that stakeholders can reference at milestone reviews.

What This Issue Log Software Development Includes

The ProjectAdm Issue Log tracks all 6 issues through their complete lifecycle:

• ISS-001 — AI API Rate Limits — Identified: Sprint 18; Owner: Henry Douglas; Priority: High; Impact: AI suggestion engine blocked on stress test (280 requests/hour vs. 100/hour OpenAI limit); Resolution: Request queuing with exponential backoff implemented by Marcus Webb (Sprint 19, 40 hrs); Status: CLOSED Sprint 20; Residual: $800/month API cost cap maintained in monitoring
• ISS-002 — MariaDB Performance on Large Boards — Identified: Sprint 13; Owner: Marcus Webb; Priority: Critical; Impact: p95 query time 4.2s on 500+ task boards (threshold: 300ms); Advanced Filtering deferred from M3; Resolution: Recursive CTE replaced with indexed views + query rewrite (Sprints 17–19, 120 hrs Marcus Webb + 60 hrs Bruno Silva); Re-test: Sprint 20 — p95 280ms (PASSED); Status: CLOSED Sprint 20
• ISS-003 — Safari Drag-and-Drop Incompatibility — Identified: Sprint 8; Owner: Julia Chen; Priority: High; Impact: Kanban drag-and-drop non-functional on Safari 17 (iOS + macOS); Resolution: HTML5 Drag-and-Drop API replaced with custom touch events + mouse events for Safari compatibility (80 hrs Julia Chen, Sprints 8–9); Verified: Safari 17.4 (iOS 17.4, macOS Sonoma 14.4); Status: CLOSED Sprint 9
• ISS-004 — Stripe Webhook Delivery Failures — Identified: Sprint 7; Owner: Henry Douglas; Priority: High; Impact: Webhook signature validation bug in PHP SDK — 3% of test webhooks failing; Resolution: Idempotency keys implemented, retry logic added, webhook validation test added to Definition of Done (Sprint 7, 16 hrs Marcus Webb); 45-day monitoring: 0 failures post-fix; Status: CLOSED Sprint 16 (after monitoring period)
• ISS-005 — Spanish Localization Incomplete — Identified: Sprint 22; Owner: Eduardo Montes; Priority: Medium; Impact: 38 UI strings untranslated at M5 (94% completion vs. 100% target); Resolution: Native-speaker translator engaged (Upwork, $800, 3 weeks); Status: CLOSED March 15, 2026 (post-launch); No impact on go-live date (post-launch feature)
• ISS-006 — PHPUnit Test Suite Runtime — Identified: Sprint 20; Owner: Lucas Park; Priority: Low; Impact: PHPUnit suite running 8.4 minutes (threshold: 10 minutes, but approaching); Resolution: Parallel test execution optimization deferred to post-launch maintenance sprint (Q2 2026); Status: OPEN (monitoring) — formally closed in post-launch roadmap
• Summary Statistics — Total issues raised: 6; Closed before go-live: 5; Open at go-live: 1 (ISS-006, low priority); Average resolution time: 3.2 sprints; No issues exceeded contingency reserve; 3 issues (ISS-001, ISS-002, ISS-006) added to Lessons Learned as recurring risk patterns for future PHP/SaaS projects

How Eduardo Montes Used This Issue Log Software Development

Eduardo Montes reviewed the Issue Log Software Development at every sprint standup — not just at sprint reviews. The daily visibility ensured no issue went unaddressed for more than 24 hours. When ISS-002 was elevated to Critical in Sprint 13, the issue log's clear impact description ("Advanced Filtering cannot be accepted at M3") gave Eduardo the specific language he needed to present the deferral decision to Henry Douglas credibly and without ambiguity.

How to Use This Issue Log Software Development Document

Use this example to understand how to structure an Issue Log Software Development that drives resolution rather than just recording problems. The ProjectAdm log's "resolution actions" column required specific tasks with owners and due dates — not generic notes like "under investigation." This specificity made every issue a mini-project with a clear path to closure.

Download the Template and Deepen Your Knowledge

Ready to create your own issue log? Download the blank Issue Log Template (PMBOK 8).

• Download the Issue Log Template — PMBOK 8 (blank, ready to use)
• Read the full guide: Issue Log in PMBOK 8

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.

Format: Microsoft Excel (.xlsx) | Project: Software Development (SaaS Platform) | PMBOK Edition: 8th (2025) | Domain: Uncertainty