Question 1

How do I convert assessment findings into Azure DevOps work items?

Accepted Answer

Run the export script with -TargetTool ADO against your assessment markdown file. It parses findings with headers like #### P0-001 and writes a CSV with ADO columns including Title, Priority, Severity, and Acceptance Criteria for direct import.

Question 2

How do I import resiliency findings into Jira from a markdown report?

Accepted Answer

Run the exporter with Jira as the target tool. It maps each finding to Jira columns (Summary, Issue Type, Priority, Description, Labels, Components) and translates P0-P3 priorities to Highest, High, Medium, and Low.

Question 3

What format must the assessment markdown follow for export to work?

Accepted Answer

Findings must use headers in the form #### Pn-###: Title (for example #### P0-001) with bolded fields like **Priority:**, **Issue:**, **Recommended Fix:**, and **File:**. If no headers match this pattern, the script reports that no findings were exported.

Question 4

Why did the CSV export produce zero findings?

Accepted Answer

Zero findings means the report lacks headers matching the expected #### Pn-###: Title pattern. Verify the assessment file uses P0 through P3 finding IDs and that the header level is exactly four hash marks.

Question 5

Does the export script require PowerShell or Python?

Accepted Answer

Both options exist. The primary script is export-workitems.ps1 requiring PowerShell 7 or later, while wrapper scripts (create-workitems.ps1 and create-workitems.sh) invoke an equivalent Python implementation, export-workitems.py.

hve-resiliency-workitem-export

SYSTEM DOCUMENTATION & REQUIREMENTS

Frequently Asked Questions about hve-resiliency-workitem-export

Related Skills

code-review

spec-to-workitem

technical-debt-analysis

jira-task