Getting started
Overview
What are Projects?
Organizational containers that group related testing work together.
- Group test cases, requirements, suites, and templates
- Filter and view work by project across the platform
- Track project-level statistics and progress
- Customize with colors and icons for visual identification
- Manage project lifecycle from planning to completion
- Archive old projects while preserving historical data
Key benefits
Why use projects to organize your work?
Clarity
See all work related to a specific product or feature
Filtering
Quickly filter views to show only one project's items
Context
Understand what each test case or requirement belongs to
Reporting
Generate project-specific reports and metrics
Optional but recommended
Projects are optional. You can work without them, but they provide valuable organization as your testing grows. Start using projects when you have multiple products or features to test.
Step-by-step
Creating Projects
Visual identity
Customization
Colors and icons
Personalize projects for quick visual identification.
Available icons:
Folder
General projects
Smartphone
Mobile apps
Code
Development projects
Shield
Security projects
Globe
Web applications
Database
Backend/data projects
Cloud
Cloud infrastructure
Rocket
Launch/release projects
Package
Product releases
Terminal
CLI/dev tools
Color palette:
Blue
General purpose
Green
Active development
Purple
Planning phase
Orange
In progress
Red
Critical/urgent
Pink
Design/UX
Indigo
Research
Yellow
Testing phase
Gray
On hold
Color coding strategies
How to use colors effectively across your projects.
🟢 Green = Active development
🔵 Blue = Planning phase
🟡 Yellow = Testing in progress
🟣 Purple = Awaiting release
⚪ Gray = On hold
Choose a system
Pick one color coding strategy and stick with it across all projects for consistency.
Using projects
Organization
Assigning items to projects
How to link test cases, requirements, suites, and templates to projects.
Test Cases
• During test case creation
• When editing test cases
• Via bulk update operations
Requirements
• During requirement creation
• When editing requirements
• Automatically links to generated test cases
Test Suites
• During suite creation
• When editing suite details
• Optional assignment
Templates
• Coming soon
• Will support project assignment
• For project-specific settings
Status management
Project Lifecycle
Project statuses
Track project progress through different phases.
Active
Currently being worked on
On Hold
Temporarily paused
Completed
Finished and delivered
Archived
No longer active, hidden from main view
Status changes
Change status by editing the project. Status doesn't affect functionality - it's purely for organization and tracking.
Finding projects
Filtering & Search
Quality
Best Practices
Effective project organization
Strategies for structuring your projects.
✅ Do
- Create projects for distinct products/features
- Use clear, descriptive names
- Choose consistent color/icon schemes
- Archive completed projects regularly
- Update status as projects progress
- Add meaningful descriptions
❌ Avoid
- Too many small, granular projects
- Generic names like "Project 1"
- Random color choices without system
- Leaving all projects as "Active" forever
- Creating projects for temporary work
- Forgetting to archive old projects
Project structure patterns
Common ways to organize projects.
One project per product or application:
• Mobile App iOS
• Mobile App Android
• Web Application
• Admin Dashboard
• Public API
Best for: Teams with multiple distinct products
When to create a project
Deciding if you need a new project.
Create a project when:
- Testing a new product or major feature that will have ongoing work
- Starting a distinct testing initiative (e.g., security audit)
- Managing work that spans multiple sprints or releases
- Needing to separate reporting and metrics by product/area
Don't create a project when:
- Testing a small bug fix or minor feature (use existing project)
- Work is temporary or one-time (doesn't need long-term organization)
- You're just starting and have only a few test cases
- The work fits well within an existing project
Maintenance schedule
Keep your projects organized over time.
Regular maintenance:
- Monthly: Review project statuses, update to reflect current state
- Quarterly: Archive completed projects, review if all projects are still needed
- After releases: Mark projects as completed or archived
- As needed: Update descriptions when project scope changes
FAQ
Frequently Asked Questions
Help
Support
Getting help
Resources for project management assistance.
Contact options:
- Email: support@synthqa.app
- Use the feedback button in your dashboard
- Visit our knowledge base for examples
When requesting project support:
- Describe your team structure and testing needs
- Share your current project organization challenges
- Explain what you're trying to achieve
- Include screenshots if reporting UI issues
Last updated: January 2026 · Guide version: 1.0