A run finishes, somebody reads it, and what they conclude has to stay with the
run. The next reader then starts from the conclusion instead of from the raw
output.
Notifications
The bell at the top of the window holds the notifications of the account.
A notification carries one of four levels: information, success, warning or
error.
The browser holds one request open, and the server answers the moment that
something newer exists, or after half a minute with nothing. A quiet system
costs two requests per minute for each reader, and a busy one delivers in
milliseconds.
Comments and notifications¶
A run finishes, somebody reads it, and what they conclude has to stay with the run. The next reader then starts from the conclusion instead of from the raw output.
Comments¶
A comment hangs on one of three records: a test run, an analysis run, or a monitored device. The comment dock on the right side of the screen holds the thread of the record that is open.
A comment body accepts two kinds of markup:
@loginA mention of an account. The mention must start a word, so
user@example.comis an address and not a mention. Midair drops a name that no account answers to.#kind.idA reference to another record, for example
#test.10. The reference must start a word.Who hears about a comment¶
Midair tells two groups of people, and it tells nobody twice:
everybody that the comment names with
@login;the account that started the run.
The author of a comment receives nothing about their own comment.
Each recipient gets a notification in the browser and an e-mail. The e-mail needs a configured mail server. See Integrations.
Notifications¶
The bell at the top of the window holds the notifications of the account.
A notification carries one of four levels: information, success, warning or error.
The browser holds one request open, and the server answers the moment that something newer exists, or after half a minute with nothing. A quiet system costs two requests per minute for each reader, and a busy one delivers in milliseconds.
Visibility¶
A comment record carries the workspace of the record that it is about. The workspace decides who may read the comment, in the same way as it decides who may read the run. See Users, teams and access.