Product Design Case Study

Bugasura — Version History

How might we help QA Leads understand requirement changes, compare previous versions, and identify test cases impacted by those changes?

Problem FramingMVPFeature PrioritizationUX Design

Overview

While exploring Requirements and Test Case workflows on the Bugasura website, I identified a gap in how requirement changes are preserved and communicated across linked test cases. This case study explores a Version History solution focused on improving traceability and change visibility.

I focused on QA Leads as the primary user, as they oversee requirement reviews, test planning, and release quality across QA teams. The solution helps them quickly understand requirement changes and identify linked test cases that may need review.

Role: Product Design / Product Thinking
Focus: Problem Framing · MVP · Prioritization · UX Design
Primary User: QA Lead

Proposed Solution

I proposed a Version History experience that allows QA Leads to identify when a requirement has changed, review previous versions, compare revisions, and restore an earlier version when needed. Changes are also surfaced on linked test cases through an “Action Required” indicator, helping QA teams identify coverage that may need review.

Requirement ChangeVersion HistoryCompare / RestoreImpacted Test Case

A few key wireframes from the proposed experience are shown below. Click any image to view it larger.

Requirement discovery

Current Experience

Requirement edits are recorded in Activity, but there is no clear visual indication on the requirement itself that it has changed.

Proposed Experience

A “Modified” indicator makes requirement changes discoverable without requiring users to open the requirement.

Requirement history

Current Experience

Activity shows who edited the requirement and when, but previous content cannot be reviewed or compared.

Proposed Experience

Version History preserves previous revisions and gives users a way to review changes.

Test case impact

Current Experience

Linked test cases do not surface that the underlying requirement has changed.

Proposed Experience

Impacted test cases surface an “Action Required” indicator so QA teams know which coverage may need review.

Six wireframes were created to cover the complete experience, including the entry point, version history, comparison, restore, impacted test cases, and empty state.

Explore the Full Work

Product Design Document

Problem framing, primary user, MVP scope, prioritization, design decisions, success metrics and open questions.

Wireframes

Six wireframes covering requirement change discovery, Version History, comparison, restore, impacted test cases and empty states.

Product Walkthrough

A short walkthrough of the existing workflow, the identified gap, and the proposed solution.

Key Learnings

Understand before solving

Looking at the existing workflow first helped me identify the actual gap instead of assuming the solution upfront.

Prioritize the core problem

I learned to separate the must-have experience from enhancements that could be introduced later.

Design with the existing product in mind

The goal wasn't to redesign Bugasura, but to add the missing experience while keeping the workflow familiar.

This project helped me strengthen my approach to product discovery, prioritization, and designing solutions around real user workflows.

Skills & Methods

Problem FramingMVPFeature PrioritizationUX Design