Jira Work Explorer

Contributors🕹️Myles Henaghan

When you have only one or two tickets and need to quickly understand what they are, where they sit (story, epic, initiative), and what related work has moved, use this skill.

Intent

Given seed issues, build a deterministic associated-work map:

• parent chain (story -> epic -> initiative)
• direct children
• subtasks
• linked issues
• status/type summaries across discovered work

Script path

• library/skills/jira-work-explorer/scripts/jira-work-explorer.mjs

Inputs

• One or more --issue-key values, or
• A --jql query

Output

JSON with:

• discovered issues and normalized metadata
• graph edges and relationship type
• summary counts by issue type and status

Examples

Start from two stories:

node library/skills/jira-work-explorer/scripts/jira-work-explorer.mjs \
  --issue-key PIPE-703 \
  --issue-key PIPE-704 \
  --out /tmp/jira-work-explorer/itda5-703-704.json

Start from a parent epic:

node library/skills/jira-work-explorer/scripts/jira-work-explorer.mjs \
  --issue-key PIPE-629 \
  --max-issues 200

JQL entry point:

node library/skills/jira-work-explorer/scripts/jira-work-explorer.mjs \
  --jql "project = PIPE AND text ~ \"Storefront\" ORDER BY updated DESC" \
  --max-issues 100

Notes

• This script is deterministic and read-only.
• It reuses shared Jira helpers from the cycle-time skill scripts to avoid duplication of auth, env loading, and Jira API transport logic.
• Use jira-cycle-time-diagnostic when you specifically need wait/cycle metrics.