The Bug Settings section in Orangescrum Cloud gives you full control over how issues and bugs are categorized, tracked, and resolved within your projects.
Here, workspace admins can define custom attributes — such as Severity, Category, Issue Type, Root Cause, and Resolution — to standardize bug reporting and ensure consistency across teams.
By tailoring these settings to your workflow, you can streamline your QA process, improve collaboration between testers and developers, and gain better visibility into defect patterns and priorities.
Example: QA teams can classify bugs by severity (Critical, Major, Minor), track affected versions, and record root causes to prevent recurring issues.
Why Use Bug Settings
- Standardize issue tracking across all projects and teams.
- Prioritize effectively with clearly defined severity and categories.
- Enable detailed analysis by linking bugs to causes, versions, and resolutions.
- Customize your workflow to match your QA, UAT, or production process.
- Improve reporting accuracy for bug trends, fix rates, and release quality.
Accessing Bug Settings
- Go to Settings → Bug Settings.
- You’ll find configurable sections such as:
- Severity – Define the impact level of a bug.
- Category – Classify bugs based on functionality or module.
- Issue Type – Specify the type of defect (e.g., Bug, Enhancement, Request).
- Activity Type – Track related test or development activities.
- Phase – Identify which stage (UAT, QA, Production) the issue occurred in.
- Root Cause – Record the underlying cause for process improvement.
- Fix Version / Affect Version – Link defects to release versions.
- Origin – Capture where the issue originated.
- Resolution – Document how the issue was fixed or handled.