← ClaudeAtlas

jira-ticket-historylisted

Render the complete history of one Jira ticket as a local HTML page styled like `git log` — every changelog entry, comment and worklog as a "commit" with author and time, click to expand what changed, description and text-field edits as line diffs with a full-text view, titles as word diffs, and filters by activity type (status, assignee, description, title, other fields, comments, issue links, web links, attachments, worklogs) plus a hide-automation switch. Pages through every endpoint so nothing is silently cut off, and works on any Jira Cloud or Data Center site via an Atlassian MCP or an API token. Use when the user asks for a ticket's history, changelog, audit trail or timeline, "what changed on ABC-123", "who changed the description", "show me the git log of this ticket", or pastes a Jira ticket URL wanting its history. Read-only; configured once, overridable per run.
vslipchenko/ai · ★ 0 · AI & Automation · score 70
Install: claude install-skill vslipchenko/ai
# Jira Ticket History Turn one Jira ticket's full history into a single self-contained HTML page that reads like `git log`: one line per change, newest first, click a line to see exactly what changed. The history is spread across three Jira APIs that each know part of it — the changelog (field edits), comments, and worklogs — and every one of them returns a page at a time. This skill collects all of them to the end, normalises them into "commits", and renders them through a fixed template, so the page looks the same on every run and on every site. `<SKILL_DIR>` below is this skill's own announced base directory (the path shown when this skill loads, ending in `.../skills/jira-ticket-history`). Scripts are at `<SKILL_DIR>/scripts/`, the page template at `<SKILL_DIR>/assets/`, references at `<SKILL_DIR>/references/`. **Config lives at `~/.jira-ticket-history/config.json`** — the user's home directory, not this repo. It is written once and reused every run. This skill is **read-only against Jira**. It only reads; it never edits a field, transitions, comments, logs work or changes anything else on the ticket. Never call a write operation, even if one is available and even if asked mid-run to "just fix" something — say that this skill only reads. ## Prerequisites **Hard requirements** — without these the skill cannot run at all: - **Python 3 or Node ≥ 18** for the bundled scripts. Either is fine; they are twins. If neither exists, say so and stop — see Step 5 for the ord