hve-resiliency-workitem-jira-import

Bulk-creates Jira Cloud issues from a resiliency export CSV via the Jira REST API v3.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/christopherromero/HVE-Resiliency --skill hve-resiliency-workitem-jira-import-christopherromero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hve-resiliency-workitem-jira-import
Source: https://github.com/christopherromero/HVE-Resiliency/tree/main/.github/skills/hve-resiliency-workitem-jira-import
Command: npx skills add https://github.com/christopherromero/HVE-Resiliency --skill hve-resiliency-workitem-jira-import-christopherromero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually recreating dozens of resiliency assessment findings as Jira issues is slow and error-prone. This Skill automates the bulk creation of Jira Cloud issues from a structured CSV export, preserving priorities, descriptions, and hierarchy. ## Core Features & Use Cases - Bulk Issue Creation: Posts each CSV row to Jira Cloud via POST /rest/api/3/issue, converting descriptions into Atlassian Document Format (ADF) with bold keys, inline code, and code blocks. - Hierarchical Structure: Creates a parent Epic summarizing the assessment, optional P0–P3 priority group Stories, and links every finding as a child issue. - Assessment Attachment: Automatically uploads the assessment markdown file as an attachment on the parent issue. - Use Case: After running a resiliency assessment that produced 40 prioritized findings, import them all into your Jira project in one command, grouped by priority under a single Epic, instead of creating each ticket by hand. ## Quick Start Run the hve-resiliency-workitem-jira-import skill with your Jira base URL, project key, email, API token, and the path to the export CSV to bulk-create the issues.

Frequently Asked Questions about hve-resiliency-workitem-jira-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bulk-create Jira issues from a CSV file?

Run the import-jira.ps1 script with -CsvPath, -BaseUrl, and -ProjectKey, plus credentials via -Email/-ApiToken or the JIRA_EMAIL and JIRA_API_TOKEN environment variables. Each CSV row is posted to Jira Cloud via the REST API v3 as a new issue.

How do I group imported Jira issues by priority under an Epic?

Pass the -GroupByPriority switch. The script creates one parent Epic, inserts one Story per non-empty P0–P3 bucket under it, and links each finding to its matching priority group using the parent field.

Does the Jira import work with company-managed projects?

It works when the project accepts the parent field for the issue types used. For legacy company-managed projects requiring Epic Link, pass -EpicNameField with your Epic Name custom field id, or import with -NoParent and link manually.

Why does Jira issue creation fail with a 400 or 403 error?

A 403 means the account lacks Create Issue or Add Attachment permission. A 400 usually means the issue type does not exist in the project (override with -GroupType or -ChildType) or the parent field is not allowed for that issue type.

Can I validate the CSV before creating Jira issues?

Yes, use the -DryRun switch. It parses the CSV, shows the planned parent, priority groups, and each row's issue type and summary without making any API calls or requiring credentials.