[Extension]: Jira Integration (Sync Engine) v0.5.0 (version update of jira-sync)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- json
- Domain
- tooling
Research direction
Locate the existing jira-sync catalog entry and compare it with the proposed catalog entry in this issue. Update only the version, download URL, command count, and updated_at while preserving created_at, then run the catalog validation checks to confirm the entry remains valid.
Written by the indexing model from the issue text.
Description
Note for triage: version update of the existing catalog entry
jira-sync→0.5.0(re-filed via this template per the maintainer process; direct-JSON catalog PRs are now redirected here).
Extension ID
jira-sync
Extension Name
Jira Integration (Sync Engine)
Version
0.5.0
Description
An idempotent, drift-aware, fail-closed reconcile engine that mirrors spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase).
Author
Ash Brener
Repository URL
https://github.com/ashbrener/spec-kit-jira-sync
Download URL
https://github.com/ashbrener/spec-kit-jira-sync/archive/refs/tags/v0.5.0.zip
License
MIT
Homepage (optional)
https://github.com/ashbrener/spec-kit-jira-sync
Documentation URL (optional)
https://github.com/ashbrener/spec-kit-jira-sync/blob/main/README.md
Changelog URL (optional)
https://github.com/ashbrener/spec-kit-jira-sync/blob/main/CHANGELOG.md
Required Spec Kit Version
=0.1.0
Number of Commands
4
Tags
issue-tracking, jira, tasks-sync, reconcile, drift-aware
Testing Checklist
- Extension installs successfully via download URL
- All commands execute without errors
- Documentation is complete and accurate
- No security vulnerabilities identified
- Tested on at least one real project
Submission Requirements
- Valid
extension.ymlmanifest included - README.md with installation and usage instructions
- LICENSE file included
- GitHub release created with version tag
- All command files exist and are properly formatted
- Extension ID follows naming conventions (lowercase-with-hyphens)
Testing Details
Released v0.5.0 with a published source archive (pre-flight verified HTTP 200 at the download URL). Full offline test suite (bats + shellcheck + yamllint + markdownlint) green in CI on macOS + Linux; dogfooded against a live Jira project.
Example Usage
specify extension add jira-sync --from https://github.com/ashbrener/spec-kit-jira-sync/archive/refs/tags/v0.5.0.zip
Proposed Catalog Entry
{
"jira-sync": {
"name": "Jira Integration (Sync Engine)",
"id": "jira-sync",
"description": "An idempotent, drift-aware, fail-closed reconcile engine that mirrors spec-kit specs into Jira (Epic per repo, Story per spec, Subtask per phase).",
"author": "Ash Brener",
"version": "0.5.0",
"download_url": "https://github.com/ashbrener/spec-kit-jira-sync/archive/refs/tags/v0.5.0.zip",
"repository": "https://github.com/ashbrener/spec-kit-jira-sync",
"homepage": "https://github.com/ashbrener/spec-kit-jira-sync",
"documentation": "https://github.com/ashbrener/spec-kit-jira-sync/blob/main/README.md",
"changelog": "https://github.com/ashbrener/spec-kit-jira-sync/blob/main/CHANGELOG.md",
"license": "MIT",
"requires": { "speckit_version": ">=0.1.0" },
"provides": { "commands": 4, "hooks": 0 },
"tags": ["issue-tracking", "jira", "tasks-sync", "reconcile", "drift-aware"],
"verified": false,
"downloads": 0,
"stars": 0,
"updated_at": "2026-08-12T00:00:00Z"
}
}
Additional Context
Version bump of the existing jira-sync entry; only version, download_url, provides.commands, and updated_at change. Preserve the existing created_at. Thanks for maintaining the catalog!
- Dominant language
- Python
- Stars
- 138k
- Forks
- 12.4k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 136
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/spec-kit
-
enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement needs-triage triage-can-wait
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
extension-submission triage-can-wait
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100