Skip to content

docs: custom workflow status mapping parity across PM providers#1377

Merged
aaight merged 1 commit into
devfrom
docs/MNG-1068-custom-status-pm-providers
May 18, 2026
Merged

docs: custom workflow status mapping parity across PM providers#1377
aaight merged 1 commit into
devfrom
docs/MNG-1068-custom-status-pm-providers

Conversation

@aaight
Copy link
Copy Markdown
Collaborator

@aaight aaight commented May 18, 2026

Summary

Documents the custom workflow status mapping support shipped for Trello, JIRA, and Linear (MNG-1064/1065/1066/1067) so operators have a clear setup story and contributors know the provider parity contract.

https://linear.app/issue/MNG-1068

Changes

  • docs/architecture/04-agent-system.md — adds a Custom workflow statuses across PM providers subsection that explains the two-part contract (status definition in code/DB + provider-native mapping in integration config), lists each provider's dispatch path (TrelloCustomStatusChangedTrigger, JiraStatusChangedTrigger, LinearStatusChangedTrigger), and states the dispatch precondition that statuses without agentType render and save but do not dispatch.
  • docs/architecture/08-config-credentials.md — adds a Custom workflow status mappings subsection with the per-provider native value table (Trello lists.<customKey>, JIRA statuses.<customKey>, Linear statuses.<customKey>), the lifecycle-resolver spread requirement, and the auto-create-trigger-config behavior on wizard save.
  • docs/architecture/09-database.md — adds the missing workflow_status_definitions table and workflowStatusDefinitionsRepository entries.
  • docs/getting-started.md — adds a Map a custom workflow status operator walkthrough under step 10 (Configure Triggers): register with cascade workflow-statuses create, map in the wizard's Status Mapping step, and verify with cascade projects trigger-list / dashboard Agent Configs tab. Documents the render-only path for statuses without --agent-type.
  • src/integrations/README.md — adds the Custom workflow status — provider parity contract section: where each concern lives (status definition table vs provider-native mapping), wizard path (trpc.workflowStatuses.list + StatusMappingStep + buildMissingStatusTriggerConfigs), dispatch path (shared resolvePMStatusAgentFromWorkflowDefinitions), and a four-item checklist a new PM provider must implement for parity.

All four files cross-reference each other through relative ./*.md links, and the agentType: null render-but-don't-dispatch invariant is stated consistently in every file.

Test plan

  • npx vitest run --project unit-core tests/unit/architecture-docs.test.ts — passes (41 tests, including the relative-link guard that now covers the new cross-references).
  • npx vitest run --project unit-core tests/unit/integrations/ — passes (258 tests including pm-conformance harness).
  • npm run typecheck — passes.
  • Verified each doc claim against the actual implementation (buildMissingStatusTriggerConfigs, TrelloCustomStatusChangedTrigger, resolvePMStatusAgent*FromWorkflowDefinitions, LinearIntegration.resolveLifecycleConfig spread pattern).

🕵️ claude-code · claude-opus-4-7 · run details

@codecov
Copy link
Copy Markdown

codecov Bot commented May 18, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copy link
Copy Markdown
Collaborator

@nhopeatall nhopeatall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - the documentation matches the shipped custom workflow status behavior across Trello, JIRA, and Linear. I verified the CLI examples, provider-native storage shapes, lifecycle status spreading, shared wizard save helper, and PM trigger dispatch/resolver paths; the architecture-docs unit test also passes locally.

🕵️ codex · gpt-5.5 · run details

@aaight aaight merged commit e865e34 into dev May 18, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants