List Jiras

List JIRAs

This skill provides functionality to query JIRA bugs for a specified project and return raw issue data. It uses the JIRA REST API to fetch complete bug information with all fields and metadata, without performing any summarization.

When to Use This Skill

Use this skill when you need to:

• Fetch raw JIRA issue data for further processing
• Access complete issue details including all fields
• Build custom analysis workflows
• Provide data to other commands (like summarize-jiras)
• Export JIRA data for offline analysis

Prerequisites

1. Python 3 Installation

   • Check if installed: which python3
   • Python 3.6 or later is required
   • Comes pre-installed on most systems

2. JIRA Authentication

   • Requires environment variables to be set:
     • JIRA_URL: Base URL for JIRA instance (e.g., "https://redhat.atlassian.net")
     • JIRA_USERNAME: Your JIRA username (email address) for Basic auth
     • JIRA_API_TOKEN: Your JIRA API token
   • How to get a JIRA API token:
     • Navigate to https://id.atlassian.com/manage-profile/security/api-tokens
     • Generate a new API token
     • Export it as an environment variable

3. Network Access

   • The script requires network access to reach your JIRA instance
   • Ensure you can make HTTPS requests to the JIRA URL

Implementation Steps

Step 1: Verify Prerequisites

First, ensure Python 3 is available:

python3 --version

If Python 3 is not installed, guide the user through installation for their platform.

Step 2: Verify Environment Variables

Check that required environment variables are set:

# Verify JIRA credentials are configured
echo "JIRA_URL: ${JIRA_URL}"
echo "JIRA_USERNAME: ${JIRA_USERNAME}"
echo "JIRA_API_TOKEN: ${JIRA_API_TOKEN:+***set***}"

If any are missing, guide the user to set them:

export JIRA_URL="https://redhat.atlassian.net"
export JIRA_USERNAME="your-email@redhat.com"
export JIRA_API_TOKEN="your-api-token-here"

Step 3: Locate the Script

The script is located at:

plugins/teams/skills/list-jiras/list_jiras.py

Step 4: Run the Script

Execute the script with appropriate arguments:

# Basic usage - all open bugs in a project
python3 plugins/teams/skills/list-jiras/list_jiras.py \
  --project OCPBUGS

# Filter by component
python3 plugins/teams/skills/list-jiras/list_jiras.py \
  --project OCPBUGS \
  --component "kube-apiserver"

# Filter by multiple components
python3 plugins/teams/skills/list-jiras/list_jiras.py \
  --project OCPBUGS \
  --component "kube-apiserver" "Management Console"

# Include closed bugs
python3 plugins/teams/skills/list-jiras/list_jiras.py \
  --project OCPBUGS \
  --include-closed

# Filter by status
python3 plugins/teams/skills/list-jiras/list_jiras.py \
  --project OCPBUGS \
  --status New "In Progress"

# Set maximum results limit (default 100)
python3 plugins/teams/skills/list-jiras/list_jiras.py \
  --project OCPBUGS \
  --limit 500

Step 5: Process the Output

The script outputs JSON data with the following structure:

{
  "project": "OCPBUGS",
  "total_count": 1500,
  "fetched_count": 100,
  "query": "project = OCPBUGS AND (status != Closed OR (status = Closed AND resolved >= \"2025-10-11\"))",
  "filters": {
    "components": null,
    "statuses": null,
    "include_closed": false,
    "limit": 100
  },
  "issues": [
    {
      "key": "OCPBUGS-12345",
      "fields": {
        "summary": "Bug title here",
        "status": {
          "name": "New",
          "id": "1"
        },
        "priority": {
          "name": "Major",
          "id": "3"
        },
        "components": [
          {"name": "kube-apiserver", "id": "12345"}
        ],
        "assignee": {
          "displayName": "John Doe",
          "emailAddress": "jdoe@example.com"
        },
        "created": "2025-11-01T10:30:00.000+0000",
        "updated": "2025-11-05T14:20:00.000+0000",
        "resolutiondate": null,
        "versions": [
          {"name": "4.21"}
        ],
        "fixVersions": [
          {"name": "4.22"}
        ],
        "customfield_10855": "4.22.0"
      }
    },
    ...more issues...
  ],
  "note": "Showing first 100 of 1500 total results. Increase --limit for more data."
}

Field Descriptions:

• project: The JIRA project queried
• total_count: Total number of matching issues in JIRA (from search results)
• fetched_count: Number of issues actually fetched (limited by --limit parameter)
• query: The JQL query executed (includes filter for recently closed bugs)
• filters: Applied filters (components, statuses, include_closed, limit)
• issues: Array of raw JIRA issue objects, each containing:
  • key: Issue key (e.g., "OCPBUGS-12345")
  • fields: Object containing all JIRA fields for the issue:
    • summary: Issue title/summary
    • status: Status object with name and ID
    • priority: Priority object with name and ID
    • components: Array of component objects
    • assignee: Assignee object with user details
    • created: Creation timestamp
    • updated: Last updated timestamp
    • resolutiondate: Resolution timestamp (null if not closed)
    • versions: Affects Version/s array
    • fixVersions: Fix Version/s array
    • customfield_10855: Target Version (custom field)
    • And many other JIRA fields as applicable
• note: Informational message if results are truncated

Important Notes:

• By default, the query includes: Open bugs + bugs closed in the last 30 days
• This allows tracking of recent closure activity alongside current open bugs
• The script fetches a maximum number of issues (default 1000, configurable with --limit)
• The total_count represents all matching issues in JIRA
• The returned data includes ALL fields for each issue, providing complete information
• For large datasets, increase the --limit parameter to fetch more issues
• Issues can have multiple components
• All JIRA field data is preserved in the raw format

Step 6: Present Results

Based on the raw JIRA data:

1. Inform the user about the total count vs fetched count
2. Explain that the raw data includes all JIRA fields
3. Suggest using /teams:summarize-jiras if they need summary statistics
4. The raw issue data can be passed to other commands for further processing
5. Highlight any truncation and suggest increasing --limit if needed

Error Handling