jira

Extract, create, and modify JIRA stories from Mozilla JIRA (mozilla-hub.atlassian.net). Use when the user asks to create JIRA stories, update JIRA issues, search for stories, list epics, add comments, or work with sprints. Supports Markdown formatting in descriptions and comments.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "jira" with this command: npx skills add jwmossmoz/agent-skills/jwmossmoz-agent-skills-jira

JIRA

Interact with Mozilla JIRA via scripts/extract_jira.py.

Prerequisites

export JIRA_API_TOKEN="your-api-token"  # From https://id.atlassian.com/manage-profile/security/api-tokens
export JIRA_EMAIL="your@email.com"

Optional: JIRA_OUTPUT_DIR, JIRA_DEFAULT_PROJECT. Precedence: CLI args > env vars > config.toml > defaults.

Usage

uv run ~/.claude/skills/jira/scripts/extract_jira.py [options]
OperationCommand
Query current sprint--current-sprint --summary
Query your issues--my-issues
Query specific issue--jql "key = RELOPS-123"
Create issue--create --create-summary "Title"
Modify issue--modify RELOPS-123 --set-status "In Progress"
Append description--modify RELOPS-123 --append-description "New notes"
Edit comment--modify RELOPS-123 --edit-comment 1242534 --comment-body "Updated content"
Link issues--modify RELOPS-123 --link-issue RELOPS-456
Output to stdout--stdout --quiet

Markdown Formatting

Use standard Markdown for descriptions and comments. The tool automatically converts Markdown to Atlassian Document Format (ADF).

DO NOT use old Jira wiki markup syntax like [text|url] - it will not render correctly.

ElementCorrect (Markdown)Wrong (Wiki Markup)
Links[text](https://url)[text|https://url]
Bold**text***text*
Lists- item or 1. item* item or # item
Code`code` or code {code}code{code}
Headings## Headingh2. Heading

Creating Stories

When creating JIRA stories, follow this workflow:

  1. Draft the story - Create the summary and description based on requirements
  2. Humanize the description - Use /humanizer to remove AI writing patterns from the description text
  3. Submit the story - Use the humanized description with --create

Example Workflow

# 1. Draft description (you do this in memory)
# 2. Run humanizer on the description
# 3. Create story with humanized description
uv run ~/.claude/skills/jira/scripts/extract_jira.py --create \
  --create-summary "Implement new feature" \
  --description "The feature adds capability to process tasks. It handles edge cases and provides error handling." \
  --epic-create RELOPS-2019

Use /humanizer to remove AI writing patterns from story descriptions before submitting.

Resources

  • Full examples: references/examples.md
  • All options: uv run ~/.claude/skills/jira/scripts/extract_jira.py --help
  • Output: ~/moz_artifacts/jira_stories.json (default)

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

jira

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

jira

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

redash

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

os-integrations

No summary provided by upstream source.

Repository SourceNeeds Review