Quality Assurance Issue

Quality assurance issues reported through email or informal channels give QA teams and developers an inconsistent record of what the problem is, where it occurs, how reliably it can be reproduced, and what environment it was observed in. Screenshots and logs arrive as separate email attachments. Priority and issue type are not captured consistently. Review status is tracked informally rather than within the issue record itself. Without a structured, centralized QA reporting process, managing and prioritizing the issue backlog accurately requires more effort than it should.

The Quality Assurance Issue template for SharePoint, built with Infowise Ultimate Forms, provides a structured issue report form that captures submission details, the project or product and component affected, issue title and description, issue type, priority, reproducibility, operating system and browser or device context, supporting file uploads, additional notes, and a reviewer section capturing the reviewer name, date reviewed, and review status. Every report is stored as a complete, trackable record in SharePoint.

How it works

Submission and reporter details

The form captures the date of submission, the name of the person submitting the issue, and their email address. These details ensure every report is clearly attributed and that the QA team or developer assigned to the issue has a direct contact for follow-up without searching for the reporter's information separately.

Project, component, and issue identification

The form captures the project or product affected and optionally the specific component or module where the issue was observed. A clear issue title and a detailed description field give the reporter the structure needed to document the problem precisely, and give the QA team a headline view of every issue in the list without opening each record individually.

Issue type, priority, and reproducibility

Structured fields capture the issue type, the priority assigned by the reporter, and how reliably the issue can be reproduced. Capturing reproducibility in a structured field is particularly valuable for QA triage — issues that are consistently reproducible require a different response than those that are intermittent or environment-dependent, and this distinction should be recorded at the point of submission rather than established through follow-up investigation.

Environment context

The form captures the operating system and the browser or device on which the issue was observed. Capturing environment context in structured fields at the point of submission gives the development team the information needed to attempt reproduction in the correct configuration without requesting this information separately, which often causes delays when the reporter is no longer in the environment where the issue was first seen.

Supporting evidence and additional notes

A file upload field allows the reporter to attach relevant screenshots, log files, or other supporting materials directly to the issue record. A free-form notes field captures any additional context the reporter wants to include. Both are stored within the same SharePoint record as the structured issue details, ensuring the development team has everything they need in a single location.

Reviewer section

A reviewer section captures the name of the QA reviewer, the date the issue was reviewed, and the current review status. Capturing review details within the same issue record creates a complete lifecycle record — from initial report through triage and review — without requiring a separate tracking system or status update process.

What you get

• A structured QA issue report capturing submission date, reporter name, email, project, and component
• Issue title, description, type, priority, and reproducibility captured in consistent structured fields
• Operating system and browser or device environment context for accurate issue reproduction
• Supporting file upload and additional notes linked directly to the issue record
• Reviewer name, review date, and review status capturing the full review lifecycle within the same record
• Every issue stored as a complete, trackable record in a standard SharePoint list
• Filterable by project, issue type, priority, reproducibility, or review status for QA backlog management
• Free for all Ultimate Forms customers, installed automatically with a single click

Built on standard SharePoint lists

The Quality Assurance Issue system is built entirely on standard SharePoint lists. There is no external data storage and no custom interface. All issue records 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.