Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Sources end to end: intake, threading, buttons and close-out, with a review per source

Abierto
  • ¿Algo no está bien?
#265 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
fastapi, python, react
Área
api, backend

Línea de trabajo

The issue links source specific work in #206–#232 and calls for an end to end review of each integration. Pick one source and read its linked issue first, then trace intake, triage, agent handling, and close out in the relevant code and tests. Add or update a test for each step; done means the flow is confirmed or a focused follow-up is filed.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug connector

Sources end to end: how items come in, how they thread, what the buttons offer, and what Close out writes back. Each line links the original issue, which keeps the full detail.

Bugs across sources
  • #206 Reply is still offered in chat, on the phone and on the Task page for sources that cannot send. (Send/approve is already gated since 20422fe9, and the "Send & close" wording is gone.)
  • #207 Pollers read one capped page and then move the watermark: monday (50), Asana (25, no modified_since), Azure DevOps, Jira, ClickUp, Linear, Teams (200), Slack (500).
  • #208 Close the task when its item ends upstream, for every tracker (only Jira and GitHub do). (Jira's batch guard is fixed for the next release.)
  • #209 Close out on a tracker item should be able to write back a comment and a status.
  • #210 Your own chat lines are triaged as work on Slack, Telegram, and Teams when the owner lookup fails.
  • #212 Replies sent on WhatsApp and Telegram are never stored, so triage never sees them.
  • #213 IMAP: store each message's Message-ID and answer that one; append sent mail to Sent on plain IMAP servers. (In-Reply-To fallback, no double "Re:", and Date/Message-ID on SMTP sends are fixed for the next release.)
End-to-end reviews, one per source

Walk one item from each source through intake, triage, agent and close out; confirm each step with a test or open a follow-up.

  • #214 monday.com: only the first 50 items per board are read
  • #215 Jira: comments ingested before their issue on the first poll; jira_account_id is one global setting
  • #216 Asana: more than 25 open tasks hides changes to the rest
  • #217 ClickUp: capped at 25, page 0 only
  • #218 Todoist: the card's help says edits are not re-filed, but they are; replies are addressed to "Todoist"
  • #219 Linear: capped at 25 per poll
  • #220 Azure DevOps: day-precision WIQL, oldest first, the same 25 every poll on a busy day
  • #221 Trello: check that the board is in the source name
  • #222 Notion: every edit of a busy page is a new row
  • #223 Sentry and PagerDuty: PagerDuty filters on creation time; a firing Sentry issue costs a triage call every poll
  • #224 GitHub: several cards read the first card for close-out and replies
  • #225 GitLab (nested-group project names are fixed for the next release)
  • #226 Outlook / Microsoft 365 mail: Graph ids are not immutable, so a moved mail may arrive twice
  • #227 Gmail and IMAP mail (see #213)
  • #228 Microsoft Teams: delta cut at 200, own lines when the lookup fails
  • #229 Slack: own messages, thread replies, raw user ids, no link, 500 cap
  • #230 WhatsApp: sent replies not stored (#212)
  • #231 Telegram: no owner identity; sent replies not stored
  • #232 Calendar: all calendars share one 60-event cap (declined Google meetings are fixed for the next release)
Lenguaje dominante
Python
Estrellas
116
Forks
22
Merge medio
8 h 45 min
PR fusionados (30 d)
41

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ldbumble/taskuary

Todos los issues de ldbumble/taskuary

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.