Skip to content

v0.3.0 — ADR mirroring + author attribution

Latest

Choose a tag to compare

@ashbrener ashbrener released this 12 Jun 12:24
· 8 commits to main since this release
e4af8f1

MINOR feature release. Two new user-facing features since v0.2.1.

ADR / decision-record mirroring (feature 005)

Each spec's research.md decision records — the Decision / Rationale / Alternatives blocks (both the bold-lead and stock-bullet grammars) — are mirrored as one idempotent comment per decision on the spec's Jira issue. Re-runs are zero-churn; a changed decision updates its single comment in place (never a duplicate). The ADR comment stream is disjoint from clarify-session comments (speckit-adr: vs speckit-note: markers) and parity-locked to the Linear sibling's ADR layout (Linear-008 parity). Carried through the neutral workstate.decisions[] floor field; the reconcile engine stays vendor-neutral. Additive and on by default — no config, no new command.

Author-based attribution (feature 007)

Opt-in two-track attribution that makes the board reflect who authored each spec:

  • an account-independent author:<handle> label stamped on the spec issue always (works for authors with no Jira account), plus
  • a Jira assignee set on create only when the author maps to a real accountId (never re-sent on update, so a manual reassignment survives — Linear bridge FR-034 semantics).

Author resolution is vendor-neutral (Owner:/Author: line wins, else first git author to add the spec dir, else a graceful unknown no-op). The email→accountId/handle mapping is the sink's job via a gitignored operator map (jira-authors.local.yml; only a .sample placeholder ships, as the map holds PII). Off by default — absent/enabled: false is byte-identical to prior behavior.

Install

The GitHub source ZIP at the v0.3.0 tag is the install artifact:
https://github.com/ashbrener/spec-kit-jira-sync/archive/refs/tags/v0.3.0.zip

Note: the v0.3.0 tag currently sits on the release/v0.3.0 branch. After release PR #14 merges, the tag will be re-pointed to the merge commit on main (matching the v0.2.0 / v0.2.1 process).