Jira Integration

What it does

The Jira integration works in both directions: it pulls Jira issues into Specky as signals (so you can see engineering work alongside customer feedback), and it pushes PRD requirements from Specky into Jira as tickets via the Execution Bridge.

This two-way connection means your product thinking and engineering execution stay in sync — requirements trace back to evidence, and tickets trace back to requirements.

When to use it

To see Jira bug reports and feature requests alongside customer feedback in the Discovery Hub

To push PRD requirements to Jira as pre-filled tickets with one click

To keep Jira tickets updated when PRD requirements change

To link Jira epics to Specky roadmap initiatives for traceability

Setup

Go to Settings → Integrations → Jira

Click Connect Jira

Enter your Jira domain (e.g. yourcompany.atlassian.net)

Authorize Specky via Atlassian OAuth

Select which Jira projects to sync

Configure field mappings (optional — map Jira custom fields to Specky signal fields)

Click Start Sync

What gets synced (Jira → Specky)

Issues: title, description, type (bug/story/epic/task), status, priority, assignee

Comments on issues

Status change history

Epic-to-story relationships

Custom fields you've configured in the field mapping

Pushing to Jira (Specky → Jira)

Use the Execution Bridge in the PRD Editor to push requirements to Jira:

Open a PRD and click Execution Bridge in the toolbar

Select Jira as the target

Review the generated ticket previews — one ticket per requirement block

Adjust titles, descriptions, assignees, and labels as needed

Click Create Tickets — tickets are created in Jira with a link back to the Specky PRD

Keeping tickets in sync: When a PRD requirement changes, open the Execution Bridge and click Sync Changes to update the linked Jira ticket. Specky shows a diff before syncing so you can review what will change.

Tips

Map your Jira issue types to Specky signal types in the field mapping settings for better classification

Use Jira labels to tag issues that should be treated as customer feedback signals (e.g. label: customer-reported)

Connect multiple Jira projects if your product spans multiple engineering teams