Design GlitchTip-to-Gitea issue filing workflow #74

Closed
opened 2026-07-02 05:43:46 -05:00 by jcwalker3 · 0 comments
Owner

Curated 2026-07-02 to reflect review consensus (issue text only; not started).

Design the orchestrated workflow that files Gitea issues from GlitchTip
errors/events.

Boundary (must state explicitly)

  • GlitchTip-to-Gitea filing is not a GlitchTip MCP capability.
  • It lives in an orchestrator / runbook / release workflow that composes
    separate GlitchTip read tools and Gitea issue tools.
  • It must not centralize credentials (no single server holding both GlitchTip
    and Gitea tokens).

Acceptance criteria

  • Explicit invocation only — no automatic filing in phase 1.
  • Dry-run / preview required before any issue is filed.
  • Gitea mutation must pass Gitea profile checks + audit logging.
  • Defines Gitea issue title/body format.
  • Defines labels such as source:glitchtip, bug, status:triage.
  • Defines GlitchTip URL / linkback behavior.
  • Defines required fields: project, environment, release, first seen, last seen,
    event count, user count, stack summary.
  • Defines redaction rules (request bodies, cookies, headers, tokens, PII, full
    stack traces).

Parent: #75. Detailed child: #78 (dedup/linking).

_Curated 2026-07-02 to reflect review consensus (issue text only; not started)._ Design the **orchestrated** workflow that files Gitea issues from GlitchTip errors/events. ## Boundary (must state explicitly) * GlitchTip-to-Gitea filing is **not** a GlitchTip MCP capability. * It lives in an **orchestrator / runbook / release workflow** that **composes** separate GlitchTip **read** tools and Gitea **issue** tools. * It **must not centralize credentials** (no single server holding both GlitchTip and Gitea tokens). ## Acceptance criteria * **Explicit invocation only** — no automatic filing in phase 1. * **Dry-run / preview required** before any issue is filed. * Gitea mutation must pass **Gitea profile checks + audit logging**. * Defines Gitea issue title/body format. * Defines labels such as `source:glitchtip`, `bug`, `status:triage`. * Defines GlitchTip URL / linkback behavior. * Defines required fields: project, environment, release, first seen, last seen, event count, user count, stack summary. * Defines redaction rules (request bodies, cookies, headers, tokens, PII, full stack traces). Parent: #75. Detailed child: #78 (dedup/linking).
jcwalker3 added the giteadesignglitchtipworkflow labels 2026-07-02 05:44:21 -05:00
sysadmin added the status:in-progress label 2026-07-02 14:47:56 -05:00
jcwalker3 removed the status:in-progress label 2026-07-02 14:57:55 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#74