[Extension]: Jira Integration (Sync Engine) v0.5.0 (version update of jira-sync)

Offen Anfängerfreundlich
#4,099 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
72/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
json
Bereich
tooling

Rechercherichtung

Den vorhandenen jira-sync-Katalogeintrag ausfindig machen und ihn mit dem in diesem Issue vorgeschlagenen Katalogeintrag vergleichen. Nur version, download URL, command count und updated_at aktualisieren, dabei created_at beibehalten, und anschließend die Katalogvalidierungsprüfungen ausführen, um zu bestätigen, dass der Eintrag weiterhin gültig ist.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

extension-submission validation-passed

Note for triage: version update of the existing catalog entry jira-sync0.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.yml manifest 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!

Vorherrschende Sprache
Python
Sterne
138k
Forks
12.4k
Ø Merge
3 T. 6 Std.
Gemergte PRs (30 T.)
136

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/spec-kit

Alle Issues in github/spec-kit

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.