feat: ticket.template for issue body skeletons - #1
Merged
Conversation
Mirror pr.template for ticket/issue descriptions: a per-repo `ticket.template` (filesystem path or Obsidian URL, "" = built-in default) used when the pipeline drafts or updates a ticket body. - schema: document the `ticket.template` field - SKILL.md: "Drafting or updating a ticket body" step, shared resolution with pr.template, and the built-in default structure (Status / Ask / Description [Background / Already-in-place / Remaining scope] / Out of scope / End-user AC / PR AC) - example: show ticket.template in the Jira enterprise example No Go change: like pr.template, the skill reads it straight from the YAML.
Refine the ticket-template guidance: keep section headings small (###), and write End-user / PR acceptance criteria into the tracker's dedicated fields (discovered via issue metadata; rich-text fields take ADF, sent in a separate update from the markdown description) instead of the description body. Falls back to description sections only when no such field exists.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a
ticket.templateconfig field — the issue/ticket-body analogue ofpr.template. The pipeline can now fill a house-style ticket skeleton when itdrafts or updates a ticket description, the same way it already does for PRs.
Changes
_schema.yml): document theticket.templatefield —""for thebuilt-in default, or a filesystem path / Obsidian URL (same resolution as
pr.template).ticket.template, keeps section headings small (###), and routesEnd-user / PR acceptance criteria into the tracker's dedicated fields
(discovered via issue metadata; rich-text fields take ADF, sent in a separate
update from the markdown description), falling back to description sections
only when no such field exists. Built-in default structure documented
(Status / Ask / Description / Out of scope + AC fields).
ticket.templatein the Jira enterprise example.No Go change: like
pr.template, the skill reads the field straight from YAML.Testing
go build ./...cleango test ./...greeninstall-skill, and exercised the flow against areal Jira issue: description rendered with
###headings, and the twoacceptance-criteria custom fields populated as ADF bullet lists.
Risk
Low. Additive, optional field (default
""= prior behaviour). Skill-only +schema docs; no launcher code paths change.