Notifications

When a build is closed, UReport evaluates all enabled notification rules for that product lane. If any rule's conditions are met by the build's test results, an email is sent immediately to the configured recipients.

Rules are scoped to a product lane (product + type) and can be further narrowed to specific build dimensions like team, browser, or stage.

Common use cases:

• Alert the QA team when a build has failing tests in a specific component
• Notify a team when their tests fail in a specific environment or version
• Watch for regressions matching a particular tag or relation group

The email contains:

• The name of the rule(s) that triggered
• Build metadata — product, type, team, version, browser, platform, stage
• Test result summary — total, pass, fail, skip counts
• A direct link to view the build in UReport

Rules are managed per product lane via the Launches page.

1. Go to Launches and apply a product + type filter
2. Click the bell icon in the toolbar to open the Notification Rules panel
3. Add, edit, enable/disable, or delete rules

Field	Required	Description
Rule Name	Yes	A label to identify the rule in the UI and in email subjects
Recipients	Yes	One or more UReport users to email. Users must have an email address set on their account.
Scope	No	Narrow the rule to specific builds — by version, team, browser, device, platform, or stage. Leave blank to match all builds of the product lane.
Statuses	No	Which test result statuses to look for — FAIL, SKIP, or PASS. Defaults to FAIL if not set.
Name / UID Pattern	No	A regular expression matched against test names and UIDs. Only tests matching the pattern are considered.
Relation Conditions	No	Filter tests by their test relation attributes — tags, teams, components, or custom fields.
Logic	No	AND — a test must satisfy all relation conditions. OR — a test must satisfy at least one condition. Only applies when multiple relation conditions are set.

A rule fires when, after a build closes, at least one test exists that satisfies ALL of the following simultaneously:

• The build matches the rule's scope (or scope is empty)
• The test's status is one of the rule's statuses
• The test's name or UID matches the name pattern (if set)
• The test's relation satisfies the relation conditions (if set)

If no conditions are configured beyond statuses, the rule fires whenever any test of a matching status exists in the build.

Logic controls how multiple relation conditions are combined. It has no effect on statuses or the name pattern.

Logic	Behaviour	Example
AND	A test must satisfy every relation condition	tags = "smoke" AND teams = "checkout-team"
OR	A test must satisfy at least one relation condition	tags = "smoke" OR tags = "regression"

Relation conditions filter by attributes stored in Test Relations — tags, teams, components, and any custom fields defined for the product lane.

Each condition has a type (e.g. tags) and one or more values (e.g. "smoke", "regression"). A test satisfies the condition if its relation has any of the selected values for that type.

Email delivery requires SMTP to be configured in Administration → System Settings under the Notification section. UReport uses Gmail SMTP.

Setting	Description
Email (sender)	The Gmail address used to send notification emails
Password	The Gmail app password (not your account password — generate one in Google Account → Security → App Passwords)
Frontend URL	The public URL of your UReport instance, used to generate the "View Results" link in the email

Yes — recipients must be existing UReport users with an email address set on their profile. Users without an email address are silently skipped even if selected as recipients.