Overview
Requirements naturally evolve as you learn more about your project. Glossa tracks all changes automatically, maintains merged requirement history, and helps you manage evolution through the conflict checker.
How Glossa Tracks Changes
Automatic change tracking:
All edits to requirements tracked
Prior and new values stored
Who made the change logged
When change was made recorded
What's tracked:
Title changes
Description changes
Priority, status, category changes
Merged requirements
Task generation
Acceptance criteria generation
Viewing Change History
On each requirement:
Change history available
See all edits over time
See who made changes
See old vs new values
Managing Evolving Requirements
Through Conflict Checker
Best practice: Use conflict detection to manage evolution
How it works:
New information captured in new requirement
Conflict checker identifies overlap with existing requirement
You merge or supersede old requirement
Change is tracked and documented
Benefits:
Clear audit trail
All source citations preserved
Team sees what changed and why
Manual Updates
You can also manually edit:
Open requirement
Update title, description, or fields
Save changes
Changes tracked automatically
Use manual updates for:
Clarifying wording
Fixing typos
Adding detail
Changing priority/status
Best Practices
Embrace Change
Requirements will evolve - this is normal
Don't try to lock everything down early
Use Glossa to track evolution transparently
Use Conflict Checker
Let new requirements come in
Review conflicts regularly
Merge/supersede as needed
Better than manually updating everything
Review Merged Requirements
Check merged requirement history
Ensure all key info preserved
Verify citations from both sources included
Communicate Changes
When major requirements change, inform team
Use requirement history to show evolution
Reference source citations for context