Administration
Configure system settings, manage users, and set up Product Lane configurations.
Product Lane Settings
Product Lane Settings allow you to customize how UReport handles test data for each Product/Type combination. Each Product Lane can have its own configuration for issue types, relation filters, and custom states.
Product Lane Settings customize the investigation workflow, filtering options, and categorization for each product/type combination in your organization.
Issue Types
Define categories used when investigating test failures.
- Defect - Product bug
- Automation - Test automation issues
- Environment - Environment problems
- Custom types with icons and colors
Relations Filter
Configure grouping and filtering options for test results.
- Default filters (components, teams, tags)
- Custom group filters
Custom States
Organization-specific test states with TTL-based auto-resolution.
When a test fails, engineers investigate the root cause and categorize it. Issue Types are those categories — labels like Defect, Automation, or Environment that describe why a test failed.
They appear in the Test Analysis view when you open a failing test and click Investigate. The investigator selects an Issue Type from a dropdown to record what kind of failure it is. This data feeds into dashboards and failure breakdowns, so the team can see at a glance how many failures are product bugs vs. flaky automation vs. environment noise.
Issue Types are configured in two levels:
- Global Issue Types — defined once in System Settings, available system-wide
- Product Lane Issue Types — each Product Lane picks which global types to expose in its investigation dropdown
Global Issue Types (System Settings)
First, define base issue types available system-wide:
- Go to Settings → System Settings → Global Issue Types
- Add issue types with Key, Label, Icon, and Color
- These become available for all Product Lanes
Product Lane Issue Types
Each Product Lane selects which issue types to use:
- Edit a Product Lane Setting
- In Issue Types section, add from "Available Types"
- Selected types appear in investigation dropdown
Keep global issue types generic (Defect, Automation, Environment) and add product-specific types at the Product Lane level.
Relation data comes from two sources that are merged at analysis time:
- TestRelation collection — A separate record per test UID/product/type, submitted via the reporter or
POST /api/test_relation. This is the primary source. - Test.info field — Attached to the test result itself when submitted. If
test.infocontainstags,teams, orcomponentskeys, they override the values from TestRelation. Any othertest.infokeys get merged into the custom relation dimensions alongsideTestRelation.customs.
If no TestRelation record exists for a test, test.info is the sole source of relation data.
Available fields and how they map to filterable dimensions:
| Source | Field | Type | Notes |
|---|---|---|---|
| TestRelation | components |
Array of {name} objects |
e.g. [{"name":"Authentication"}] |
| TestRelation | teams |
Array of {name} objects |
e.g. [{"name":"UI Team"}] |
| TestRelation | tags |
Array of {name} objects |
e.g. [{"name":"smoke"}] |
| TestRelation | customs |
Object — string keys, array-of-string values | Each key becomes its own dimension (e.g. {"Browser":["Chrome"],"OS":["Windows"]}) |
| Test.info | tags / teams / components |
Array of strings | Overrides TestRelation values when present (e.g. {"tags":["smoke","regression"]}) |
| Test.info | any other key | String or array | Merged into custom dimensions — same effect as TestRelation.customs |
Relations Filters define which of these dimensions are exposed in the UI. They appear in two places:
- Launches (test list toolbar) — A filter panel lets you narrow the visible test list by selecting specific component names, teams, tags, or custom key values.
- Dashboard widgets — When creating a Treemap, Heatmap, or Relations Group By Bar chart, you choose which dimension to group data by. The configured relations filters determine what appears in that "Group By" dropdown.
There are two types of filters you can configure per Product Lane:
Default Filters
Plain relation dimension names — add the key exactly as it appears in the data:
componentsteamstags- Any
customskey — e.g.Browser,OS,Environment
Group Filters
Custom filters that bucket relation values into named categories. Choose a base dimension (e.g. teams), then define groups that map values to category names. Useful when you have many teams or components and want to analyze at a higher level.
Example: Team Group Filter
Base relation: teams
Values in Group Filters must match exactly — including casing — with values stored in the TestRelation records.
Open Product Lane Settings
Navigate to Settings → Product Lane Settings and edit the desired Product Lane.
Go to Relations Filter Section
Scroll to "Group Filters" and click "Create Group Filter".
Configure the Filter
- Filter Name — A descriptive name (e.g., "Team Groups")
- Base Relation Type — Select which relation to group (components, teams, tags, or custom)
Define Groups
Add groups with:
- Category Name — The group label (e.g., "Frontend")
- Values — Relation values that belong to this group (press Enter to add)
Save
Click Create. The group filter will appear as a filtering option.
Values in group filters must match exactly with values in your test data. Check your test relations for correct spelling and casing.
System Settings
Analysis Settings
- Analysis time window (7–180 days)
- Advanced Analysis toggle — enables per-triage Compare By selection
Integration Settings
- Issue tracking URL (JIRA or other tracker base URL)
- Suggested issue types for triage dropdowns
Notification Settings
- SMTP email configuration
- Notification sender address
Global Issue Types
- Define system-wide issue categories
- Set icons and colors
- Available to all Product Lanes
User Management
User Creation
- Add new users directly as admin
- Set initial roles and permissions
- Approve or reject self-registered users
Role Management
- Admin — Full system access
- Operator — Test management and investigation
- Viewer — Read-only access
| Role | Permissions | Use Case |
|---|---|---|
| Admin | Full access to all features, settings, and user management | System administrators, team leads |
| Operator | Create/edit dashboards, investigate tests, manage data | QA engineers, developers |
| Viewer | View dashboards and test results (read-only) | Stakeholders, managers |
Go to Settings → Users. As an admin you can:
- View all registered and pending users
- Approve or reject pending registrations
- Promote users to operator or admin role
- Delete accounts
There is no config flag to disable signup. However, all self-registered users are created with viewer role and pending status — they cannot log in until an admin explicitly approves them. You can leave pending registrations unreviewed to effectively block access.
To create accounts without self-registration, use Settings → Users → Create User directly as an admin.
Permissions & Security
Authentication
- Secure user authentication
- Session management
Authorization
- Role-based access control
- Feature-level permissions
- Data access restrictions
- API endpoint security
Presets
A Preset is a named, saved set of product-lane filter combinations. Instead of manually adding lanes one by one each time you open the product-lane selector, you save a multi-lane view as a preset and reload it in one click.
Presets are especially useful for cross-browser or cross-environment comparisons you run regularly — e.g. a preset called "All Browsers" that always adds Chrome, Firefox, and Safari lanes at once.
Go to Settings → Presets
Navigate to the Settings page (admin or operator) and open the Presets tab.
Click "Add Preset"
Enter a name and an optional description for the preset.
Add lanes
Add one or more lanes. Each lane is a combination of the supported dimensions:
| Dimension | Notes |
|---|---|
| product | Required per lane |
| type | Required per lane |
| version | Optional |
| browser | Optional |
| platform | Optional |
| platform_version | Optional |
| team | Optional |
| stage | Optional |
| device | Optional |
Validate and save
The UI verifies that each lane exists in UReport before adding it. If a combination matches multiple lanes or none at all, the entry is rejected with an error. Click Save once all lanes are valid.
Open the product-lane selector (available in the Launches page and the widget editor). In the selector dropdown, choose from the Presets list. All lanes defined in the preset are instantly applied — replacing any currently selected lanes.
Applying a preset replaces the current lane selection. To keep existing lanes, add them individually before or after applying a preset.
Export & Import
CSV Export
- Test execution data with customizable columns
- Investigation reports and tracking data
- Build history and analytics data
- Relation metadata and test associations
- Custom column selection and ordering
PDF Export
- Dashboard snapshots with all widgets
- Individual widget exports
- High-resolution chart exports
- Printable reports for stakeholders
Navigate to Launches
Go to the Launches page and apply your desired filters.
Click Export Button
Click the export icon in the toolbar.
Configure Columns
Select which columns to include and their order.
Download
Click Export to download the CSV file.