How does it handle sync conflicts?

The skill detects mismatches between local files and JIRA updates, presenting a diff view for the user to manually resolve conflicts before applying changes.

Does this skill support custom JIRA fields?

Yes, it can map SpecWeave metadata to custom fields like Spec URL and Increment IDs to maintain strict traceability between code and JIRA.

What JIRA issue types are supported by default?

The mapping logic follows a standard hierarchy: Increments map to Epics, User Stories map to Stories, and Tasks map to Subtasks.

Can I import an existing JIRA Epic into my project?

Yes, the jira-mapper can fetch an existing Epic and its children to generate a fully structured SpecWeave increment folder locally.

SpecWeave JIRA Sync

Name: SpecWeave JIRA Sync
Author: anton-abyzov

byanton-abyzov

•

Collaboration Tools

Synchronizes SpecWeave development increments with JIRA projects by mapping technical specifications to epics, stories, and subtasks.

About

The jira-mapper skill provides a seamless bridge between SpecWeave's autonomous development framework and JIRA project management. It automates the tedious process of manual ticket creation by exporting SpecWeave increments directly into structured JIRA hierarchies—including Epics, Stories, and Subtasks—with full traceability. Beyond initial export, it supports importing existing JIRA tickets into local development specs and maintains bidirectional synchronization, ensuring that task statuses and technical requirements stay aligned across both platforms without manual data entry.

Key Features

Automatic conversion of user stories into JIRA Story tickets with acceptance criteria
Full traceability with stored JIRA keys, URLs, and sync timestamps in metadata
13 GitHub stars
Smart conflict resolution for simultaneous updates in JIRA and local specs
Hierarchical task-to-subtask mapping for granular progress tracking
Bidirectional mapping between SpecWeave increments and JIRA Epics

Use Cases

Importing legacy JIRA tickets into a SpecWeave project to begin AI-assisted development
Syncing development progress from local task lists to JIRA subtask statuses automatically
Exporting a locally drafted feature specification to JIRA for team visibility and tracking

About

Key Features

Automatic conversion of user stories into JIRA Story tickets with acceptance criteria
Full traceability with stored JIRA keys, URLs, and sync timestamps in metadata
13 GitHub stars
Smart conflict resolution for simultaneous updates in JIRA and local specs
Hierarchical task-to-subtask mapping for granular progress tracking
Bidirectional mapping between SpecWeave increments and JIRA Epics

Use Cases

Importing legacy JIRA tickets into a SpecWeave project to begin AI-assisted development
Syncing development progress from local task lists to JIRA subtask statuses automatically
Exporting a locally drafted feature specification to JIRA for team visibility and tracking