Skip to content

feat: create a ticket from a change, or a change from a ticket - #451

Merged
danielhanold merged 8 commits into
mainfrom
feat/create-a-ticket-from-a-change-or-a-change-from-a-ticket
Nov 10, 2026
Merged

danielhanold merged 8 commits into
mainfrom
feat/create-a-ticket-from-a-change-or-a-change-from-a-ticket

Conversation

@danielhanold

@danielhanold danielhanold commented Nov 10, 2026 •

Copy link
Copy Markdown
Owner

↩ Change 0584 — Create a ticket from a change, or a change from a ticket

Summary

  • docket status --json --records now reports each linked change's ticket (provider, id, url) on its records row, for active and archived changes. The changes rows are unchanged.
  • There is a new inline skill, docket-link-ticket, always run with the person present. Its link path is in SKILL.md, the push path (readiness check, refinement, one-approval draft, spec as proposed approach, create, attach, record after confirmation) is in references/create.md, and the import path is in references/import.md.
  • docket-export no longer claims ticket work in its description and points that work to the new skill.
  • The convention, the agent-layer reference, skills-and-agents, the glossary, and models-and-effort list docket-link-ticket as an inline skill. Guards and budget rows cover the new files.
  • ADR-0162: ticket work is two inline skills, split by attended linking versus updating.

Review

Reviewed at the docket-review-standard tier (0 blockers, 0 important, 3 minor).

Finding Severity Disposition
Test lacked an active change dropped by the type filter but kept in records minor fixed (270b38e)
Link path did not say where the provider and URL come from for an id-only link minor fixed (270b38e)
Push path ran the open argv without saying to resolve it from the capability catalog minor fixed (270b38e)

Testing

  • The full suite passed at 270b38e through the build gate.
  • Before merge, a live check is needed from another repository against a sandbox ticket project, covering push (shared and private, with a spec), link, and import. Steps are in the results file.

- status test: an active fix change with a complete ticket is filtered
  out of changes by the feat type filter but its records row still
  carries the ticket.
- docket-link-ticket link path: given only an id, the provider is
  tickets.provider and the URL comes from the connector's read of the
  ticket; with no connector, ask the person for the URL.
- create path: the open operation's argv is resolved from the
  capability catalog, never hard-coded.

Regenerated embedded assets and re-measured the two skill budget rows.
@danielhanold
danielhanold merged commit 6dacf97 into main Nov 10, 2026
7 checks passed
@danielhanold
danielhanold deleted the feat/create-a-ticket-from-a-change-or-a-change-from-a-ticket branch November 10, 2026 03:16
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.

1 participant