Probara tells you about events on your test cases, plans, runs, defects, and review requests in two places: the bell in the header and your e-mail inbox. Both come from the same catalog and the same account-level preferences.
What you get notified about
The catalog has five groups. Each row can reach you In-App, by E-mail, or both.
Test Case
- A comment is added to a test case you participate in
- You are newly mentioned in a test-case comment
Test Plan
- A plan test case is assigned to you
Test Run
- A run is created or started with you as default assignee
- Run test cases are assigned to you, singly or in bulk
- A run you have assigned cases in is closed or aborted
Defect
- A defect is assigned to you
- A comment is added to a defect you are assigned to or participate in
- You are newly mentioned in a defect comment
- The status changes on a defect you reported
Review
- Test reviews that I have been assigned to
- Decisions on reviews I participate in
- Edits to reviews I participate in
- Comments on reviews I participate in
- New mention in a comment
You participate in a review request when you are its author, one of its reviewers, or have commented on it. A bulk action on several review requests sends you one notification for the whole batch, with how many requests it covers, instead of one per request. See Test case review for what each Review row covers.
Channels and defaults
In-App is on for every row above — you always see these in the bell and inbox unless you turn a row off.
E-mail is on by default only for the rows that are a direct mention, a direct assignment, or a decision on a review: the three mention rows, “a plan test case is assigned to you,” “run test cases are assigned to you,” “a defect is assigned to you,” “test reviews that I have been assigned to,” and “decisions on reviews I participate in.” Every other row starts E-mail off, including edits and comments on reviews; you can turn any row on or off.
Change your preferences from Profile → Notifications (/user/notifications). Preferences are per account, not per organization — they apply the same way across every organization you belong to.
The bell and the inbox
The bell in the header shows an unread badge once you have unread notifications. Past 9 unread, the badge shows a capped label (“9+”) instead of the exact count.
Open the bell to see your inbox. Unread notifications are marked with a dot. From there you can:
- Open a notification to go to the test case, plan, run, defect, or review request it is about. Opening it marks it as read.
- Select Mark all read to mark everything as read at once.
- Select Unread to show only the notifications you have not read yet. Select it again to see all of them.
The inbox only shows notifications for your active organization — switch organizations to see that organization’s notifications. Two more things shape what you see:
- Notifications are kept for 90 days, then removed automatically.
- If you lose access to the project a notification belongs to, that notification stops showing up, even if it was already there.
E-mail language
Notification e-mails are sent in your account’s language (the Language setting in your profile). If that language is not available for a given message, the e-mail falls back to English.
Unsubscribing from e-mail
Every notification e-mail includes a one-click unsubscribe link (and the matching List-Unsubscribe header your mail client may use instead). Using it turns E-mail off for every row on your account — a single action, not one link per row.
In-App notifications keep working normally after you unsubscribe from e-mail. You can turn E-mail back on for any row at any time from Profile → Notifications.
Notifications and API tokens
Actions performed through the API with an API token still notify the people involved — an assignment or a mention made by a token behaves the same as one made by a person.