Software bugs and change requests managed through email threads, spreadsheets, or informal communication create a tracking problem that compounds as a project grows. Issues are reported inconsistently. Assignment and priority are unclear. Related issues are not linked. Resolution steps are not documented. And when a stakeholder asks for the current status of a specific bug, finding a reliable answer requires more effort than it should.
The Bug Tracker template for SharePoint, built with Infowise Ultimate Forms, provides a structured, two-tab bug and change request form that takes every issue from initial submission through assignment, task management, resolution, and closure — with color-coded views, linked tasks, and a complete resolution history — all inside SharePoint.
How it works
Issue submission — General tab
The General tab captures all the information needed to log and prioritize an issue. The title and description define what the bug or change request is. Issue type distinguishes between bug reports, change requests, and other categories relevant to your development process. The project and module fields provide organizational context for the issue. Severity and priority determine how urgently the issue needs to be addressed. A due date establishes the resolution deadline. Related issues can be linked directly within the record, creating visible connections between dependent or related bugs. Supporting files and screenshots are attached directly to the issue record.
The Assigned To column routes ownership of the issue to the appropriate developer or team member from the point of logging, ensuring there is no ambiguity about who is responsible for resolution.
Resolution and task management — Resolution tab
The Resolution tab handles everything that happens after the issue is logged. A comments field documents resolution steps, findings, and decisions as they are made — building a chronological history of how the issue was handled. The issue status is updated as work progresses, and the date closed is recorded when resolution is complete. Additional attachments relevant to the resolution — patches, test results, or supporting documentation — are stored within the same record.
A sub-list of tasks linked directly to the issue allows developers and team leads to break complex bugs into discrete, trackable action items. Each task has its own owner and status, giving the team visibility into the specific work being done to resolve an issue without requiring a separate task management system.
Color-coded issue views
The template includes color-coded list views that make issue priority and status immediately visible without opening individual records. High-severity or overdue issues are visually distinguished from lower-priority items, enabling development leads and project managers to assess the health of the issue queue at a glance.
How it works
- A two-tab bug tracking form covering full issue details on the General tab and resolution management on the Resolution tab
- Issue type, project, module, severity, priority, and due date captured in structured columns for consistent reporting and filtering
- Related issue linking creating visible connections between dependent bugs within the same record
- A sub-list of tasks linked to each issue for granular resolution tracking without a separate tool
- Resolution comments documenting the full history of steps taken from logging to closure
- Color-coded list views providing at-a-glance visibility of issue priority and status across the full queue
- Every issue stored as a structured, searchable record in a standard SharePoint list
- Free for all Ultimate Forms customers, installed automatically with a single click
Built on standard SharePoint lists
The Bug Tracker system is built entirely on standard SharePoint lists. There is no external data storage and no custom interface. All issue records, tasks, and resolution history stay inside your SharePoint environment, governed by your existing permissions and data policies. The system can be extended or adapted at any time in the browser by the administrator who manages the site.
Read detailed installation instruction.
