Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[feature]: Telegram integration

Aperta
  • Qualcosa non va?
#10,013 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Indira-kumar ci sta già lavorando.

Dal 17/10/2026.

  • #10076 di @Indira-kumar — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
api, backend

Direzione di ricerca

The issue names no files or tests. Start with the existing Slack integration, which the request uses as its model, to see how chat events, commands and user linking are wired. Done would mean the three described behaviours work: event posts to a mapped chat, a command creates a work item, and each Telegram user is linked to their Plane account. Agreeing the design with maintainers comes first.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Is there an existing issue for this?
  • I have searched the existing issues
Summary

Add a native Telegram integration, along the lines of the existing Slack integration. A workspace admin connects a Telegram bot and maps Telegram groups (or forum topics) to Plane projects. The integration then:

  1. Posts work item events to the mapped chat: created, state changed, assigned, commented, and @mentions of the linked user.
  2. Lets members create a work item from a chat message, for example with /plane create <title> or by replying to a message with a command, the same way Slack messages can become work items today.
  3. Links each Telegram user to their Plane account, so actions run with that user's own permissions instead of one shared token.
Why should this be worked on?

Slack is the only chat integration today. Many teams run their day-to-day work in Telegram groups and don't use Slack at all, so for them Plane updates stay inside the app or in email.

The demand is already visible in the community. People have built at least eight separate Plane and Telegram bridges, for example mdportnov/plane-telegram-bot (shared in discussion #7069), csmplay/plane-telegram-webhooks, andreferi3/plane-webhooks, temamint/Plane-Notifications, and the mguptahub/plane-telegram Docker image (about 3K pulls). Each one reimplements the same pieces: webhook signature checks, mapping Plane users to Telegram users, and mapping chats to projects. Several stopped after a few commits. A first-party integration would replace these one-person projects with something maintained and bring Telegram to parity with Slack.

Related requests for other chat platforms: #6001 (Mattermost) and #3416 (Rocket.Chat).

Lingua principale
TypeScript
Stelle
61.1k
Fork
6.1k
Merge medio
1g 11h
PR unite (30g)
79

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di makeplane/plane

Tutte le issue di makeplane/plane

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.