Paradaux
IssuesPAR-78Done
0

Investigate why triage isn't a valid status in the Discord bot

Log an issue as to why triage isn't a valid status via the discord bot in the Tesks project.

Comments

tesks · Jun 4, 2026, 9:42 PM

Completed via the GitHub integration — real PR #1 (commit a37fca0) merged to develop, which drove this to Done automatically.

Nuance worth deciding: the ParadauxIO/tesks repo link maps PR merge → Done, but this merge landed on develop, not a prod release. By the develop→main release convention, "merged to develop" is really Pending Release. If you want the integration to reflect that, change the repo's on-merge status to Pending Release (Integrations → GitHub → the repo), and reserve Done for the develop→main release. Left as Done for now since that's what the configured mapping did.

Activity

  • tesks commentedJun 4, 2026, 9:42 PM
  • ParadauxIO linked a commit — Commit 9d0058a — Merge pull request #1 from ParadauxIO/fix/par-78-default-triage-statusJun 4, 2026, 9:41 PM
  • ParadauxIO linked a commit — Commit a37fca0 — Seed Triage as a default workflow status (PAR-78)Jun 4, 2026, 9:41 PM
  • ParadauxIO changed status to Status → DoneJun 4, 2026, 9:41 PM
  • ParadauxIO linked a pull request — PR #1 merged — Seed Triage as a default workflow status (PAR-78)Jun 4, 2026, 9:41 PM
  • ParadauxIO linked a pull request — PR #1 open — Seed Triage as a default workflow status (PAR-78)Jun 4, 2026, 9:40 PM
  • ParadauxIO linked a commit — Commit a37fca0 — Seed Triage as a default workflow status (PAR-78)Jun 4, 2026, 9:40 PM
  • tesks changed status to Status → In ProgressJun 4, 2026, 9:37 PM
  • paradaux moved this issue — Moved to PAR (PAR-78)Jun 4, 2026, 6:28 PM
  • tesks created the issueJun 4, 2026, 5:12 PM