home / skills / codyswanngt / lisa / jira-sync

jira-sync skill

This skill syncs plan progress to a linked JIRA ticket, posting milestones, branch and PR links to keep tickets aligned.

npx playbooks add skill codyswanngt/lisa --skill jira-sync

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.3 KB

---
name: jira-sync
description: "Syncs plan progress to a linked JIRA ticket. Posts plan contents, progress updates, branch links, and PR links at key milestones. Use this skill throughout the plan lifecycle to keep tickets in sync."
allowed-tools: ["mcp__atlassian__*", "Bash", "Read", "Glob", "Grep"]
---

# JIRA Ticket Sync

Sync current plan progress to JIRA ticket: $ARGUMENTS

If no argument provided, search for a ticket URL in the active plan file (most recently modified `.md` in `plans/`).

## Workflow

### Step 1: Identify Ticket and Context

1. **Parse ticket ID** from `$ARGUMENTS` or extract from the active plan file
2. **Fetch current ticket state** via JIRA MCP (`mcp__atlassian__getJiraIssue`)
3. **Determine current milestone** by checking:
   - Does a plan file exist? → Plan created
   - Is there a working branch? → Implementation started
   - Are tasks in progress? → Active implementation
   - Is there an open PR? → PR ready for review
   - Is the PR merged? → Complete

### Step 2: Gather Update Content

Based on the current milestone:

| Milestone | Content to Post |
|-----------|-----------------|
| **Plan created** | Plan summary, branch name, link to PR (if draft exists) |
| **Implementation in progress** | Task completion summary (X of Y tasks done), any blockers |
| **PR ready** | PR link, summary of changes, test results |
| **PR merged** | Final summary, suggest moving ticket to "Done" |

### Step 3: Post Update

1. **Add a comment** to the ticket with the gathered content via JIRA MCP
2. **Update ticket fields** if applicable:
   - Add branch name to a custom field or comment
   - Add PR link to a custom field or comment
3. **Report** what was synced to the user

### Step 4: Suggest Status Transition

Based on the milestone, suggest (but don't automatically perform) a status transition:

| Milestone | Suggested Status |
|-----------|-----------------|
| Plan created | "In Progress" |
| PR ready | "In Review" |
| PR merged | "Done" |

## Important Notes

- **Never auto-transition ticket status** — always suggest and let the user confirm
- **Idempotent updates** — running sync multiple times at the same milestone should not create duplicate comments
- **Comment format** — use JIRA markdown with clear headers and bullet points

## Execution

Sync the ticket now.

Overview

This skill synchronizes plan progress to a linked JIRA ticket. It posts plan summaries, milestone updates, branch and PR links, and suggested status transitions to keep the ticket aligned with development. Use it throughout the plan lifecycle to surface progress and avoid manual updates.

How this skill works

The skill locates a JIRA ticket from an argument or by scanning the active plan file, then fetches the current ticket state via the JIRA API. It inspects the plan and repository state to determine the milestone (plan created, implementation started, active implementation, PR ready, or PR merged). Based on that milestone it constructs a JIRA-formatted comment with branch/PR links, task completion summaries, blockers, and test results, posts the comment idempotently, and optionally updates ticket fields. Finally it reports what was synced and suggests a status transition for user confirmation.

When to use it

After creating or updating a plan to publish the plan summary to JIRA
When a working branch or tasks begin to show progress
When opening a PR to add review links and test summaries to the ticket
After merging a PR to close out work and suggest moving the ticket to Done
Periodically during long-running implementation to keep stakeholders informed

Best practices

Provide the ticket URL or ID when invoking the skill to avoid ambiguous lookups
Keep plan files up to date so the sync can accurately determine milestones and task counts
Run the sync at clear milestones (plan created, PR opened, PR merged) to keep comments focused and meaningful
Review suggested status transitions before applying them; the skill never auto-transitions tickets
Use concise headers and bullet points in plans to improve the generated JIRA comment formatting

Example use cases

Sync a newly created plan so the JIRA ticket shows the plan summary and branch link
Update the ticket when task progress changes (e.g., 3 of 5 tasks complete) to notify stakeholders
Post PR links and test results when a PR is ready for review to speed reviewer onboarding
Post final summary and recommend moving the ticket to Done after merging the PR
Run periodic syncs during active implementation to surface blockers and progress to the ticket

FAQ

Will the skill change the JIRA ticket status automatically?

No. The skill suggests status transitions based on milestone but never auto-transitions; the user must confirm any status change.

How does the skill avoid duplicate comments?

It uses idempotent update logic so repeating a sync at the same milestone updates or reuses the previous comment rather than creating duplicates.

What information does the skill add to the ticket?

Depending on milestone it can add plan summaries, task completion counts, blockers, branch names, PR links, and a final summary with a suggested status.