# Telegram
recursiva has a Telegram bot. Linked to your personal chat, it sends the notifications you route to Telegram, and with Actions on it also takes replies, commands and button presses as you. Linked to a group, it tells everyone there about chosen events in some projects. Telegram is set up per server: if it is not, Settings › Notifications › Telegram says "Not set up", and email and the Inbox work as usual.
Link your chat
- Open Settings › Notifications › Telegram and press Connect Telegram. This needs a sign-in less than 10 minutes old; if yours is older, the app asks you to sign in again.
- Open the link, or scan its QR code on your phone. It works for 10 minutes.
- Press Start in Telegram. The settings page updates by itself.
- Pick What should come to Telegram?: Only what waits on me (plans, reviews and mentions), The same as email (whatever is Instantly for email), or Everything instantly. You can change each event later.
Then:
- The bot's reply to Start names your account by its masked email, with a Not me button. If someone else's link connected your chat to their account, Not me unlinks it at once.
- Your account's address gets a security email for every chat linked.
- Send a test sends a test message. Disconnect unlinks the chat and deletes its chat ID.
What arrives
Your personal chat follows the Telegram column of What reaches you where. Telegram has no digest: each event is Instantly or Off. If Due today or Cycle starts or ends is Instantly for Telegram, it comes as one message at your digest time.
On the Telegram page:
- Length: With the comment (the default), or Short: only what happened and the issue.
- Quiet hours: Deliver silently in your quiet hours (on by default), or, with it off, messages wait until the quiet hours end. With Urgent issues still get through on, an urgent issue rings through either way.
Under each message are Open (the issue in recursiva), Snooze 2h (snoozes the issue's line in your Inbox, as the app does) and ⋯ (turns the message into the issue's card, below). With Actions off, only Open.
If the chat stops taking messages, for example because you blocked the bot, the page shows a banner. Meanwhile what was set to Telegram comes by email, and the banner counts it. Press Reconnect, or unblock the bot, to resume.
Actions
The Actions switch on the Telegram page decides whether the chat can act as you.
- Off: notifications only. Each has Open alone. Commands other than
/muteand/help, buttons, replies, forwards and issue keys are answered with how to turn Actions on. A chat starts with Actions off whenever it is linked. - On: buttons, commands and replies change issues, comments and your Inbox, as you would. Turning it on needs a recent sign-in and sends a security email. Turning it off works from any session.
Everything done from the chat says "from Telegram" on its history line and comment.
Replies and issue cards
- Reply to a notification to comment on its issue. When the notification was about a comment, the reply goes in that comment's thread.
- Send an issue key alone, or up to five (
WEB-12 WEB-14), to get each issue's card: key, state, priority, title, assignees, agent, cycle, labels, due date and the last comment. - The card's buttons are State ▾, Priority ▾, Assignee ▾, Labels ▾, Snooze 2h and Open. A pick changes the issue and redraws the card, with Undo for ten minutes. A person or a label is switched on or off.
- States and labels marked Only people (such as Todo, Approved and
proposed) are not offered. No labels leaves them on. Approving is done in recursiva. - A text reply to a card is a comment on its issue.
Commands
The bot's menu in Telegram lists these. They work in your personal chat.
| Command | What it does |
|---|---|
/my |
Your My work, five at a time. |
/inbox |
Your Inbox, five at a time, with tabs Unread and All. In Unread, Read buttons per line and Mark all read. |
/find query |
Searches every workspace you can read with the query language, for example /find #WEB @me !urgent. Five at a time. |
/triage [#project] |
Open issues labelled proposed, oldest first, one card at a time, with Cancel (with Undo), Skip and Open. A "Similar:" line lists up to three open issues that look like it. |
/new Title |
Creates an issue, see below. |
/mute 2h |
Pauses everything but urgent, see below. |
/help |
The commands and the fields /new takes. |
/new
The first line is the title, with the short forms of the query language: #project, @assignee, !priority, +label, and the keys state:, cycle:, parent:, due:, start:. Lines after the first are the description.
/new Fix the sign-in page on Safari #web !high +bug
It fails after the code is typed.- Without
#project, the issue goes to the project of the last issue you created. - Without
@, you are the assignee. - An unknown name, or two values for one field, creates nothing; the bot answers with a suggestion.
- Sent as the caption of a photo or a file,
/newattaches it. An album with one/newcaption attaches every photo. /newas a reply to a card or a notification makes a sub-issue of that issue./newas a reply to someone else's message takes its text and file.- A message forwarded to the bot comes back as a draft with Create, Project ▾ and Cancel.
The bot answers with the new issue's card.
/mute
/mute 30m, /mute 2h or /mute 1d, a week at most. /mute off ends it. /mute alone shows where things stand, with 1h, 2h, Until 09:00 and Off buttons.
While muted, urgent issues still come. Everything else is not sent later: it waits in your Inbox. The Telegram page shows "Muted until …" with Resume.
Sign-in codes
With a chat linked, your sign-in code also comes to Telegram, besides email, when you sign in from a browser this account has signed in from before. The message cannot be forwarded, and the bot deletes it once the code is used, replaced or expired.
From any other browser the code goes by email only, and the chat gets a note that a sign-in was asked from a new browser, with a Not me button that voids that code.
Group chats
A group gets the events of chosen projects in one workspace, so everyone in it sees them.
- With the workspace open in the app, go to the Telegram page and press Add a group chat. The group gets that workspace's events.
- Add the bot to the group with the link: Telegram asks which group and sends the code there itself. In a group the bot is already in, send the command shown,
/link@<bot> <code>, instead. The code works for 10 minutes. - Back on the page, pick the group's Projects and Events and save. Nothing goes to the group before that.
| Event | When |
|---|---|
| New urgent issue | An issue is created as urgent, or raised to urgent. |
| Plans waiting for approval | An agent moved an issue into review. |
| Cycle starts or ends | On a cycle's first and last day, one message at 09:00 in the time zone of the person who linked the group. |
- A group gets only what the person who linked it may read in that workspace.
- The person who linked it and the workspace's admins can change its projects and events or remove it.
- Getting a code, and saving a group with more projects or events than before, needs a recent sign-in. The person who linked it gets a security email for every group linked.
- Each group message has Open only.
/helpin the group says what it gets and who linked it; the other commands are for your personal chat. - If the bot is removed from the group, the group is marked and gets nothing more until you Link again.