Push a Pilea backlog item to Jira as an issue, and the two stay in sync on status: when the issue changes in Jira - say, it gets closed - the status mirrors back onto the Pilea backlog item automatically. Your feedback backlog reflects engineering reality without anyone updating things by hand.

What you’ll need

Admin access in Pilea to connect the integration (only admins can change integration settings)
A Jira account with permission to authorize apps

How to connect Jira

In Pilea, go to Integrations in the sidebar under Data Sources.
Find Jira in the grid and click Connect.
Click Connect in the dialog. You’ll be redirected to Jira to authorize access.
Approve the requested scopes - read:jira-work and write:jira-work. Pilea also registers a webhook, which is what powers the status mirroring.
Once you’re back, you’ll see Connected successfully!

Credentials are encrypted at rest, and you can disconnect anytime from the integration’s config dialog.

ℹ️ Note: Jira connects at the organization level, so every workspace in your organization can export to it once it’s connected.

How to export a backlog item

Open the backlog item and go to its Details tab.
Under Export to Issue Tracker, choose the Jira export option.
Pilea lists your Jira projects - pick where the issue should go.
Confirm, and Pilea creates the issue in Jira.

Already-exported items show a link to the Jira issue, so you can jump to it and avoid duplicate exports.

How the two-way status sync works

The webhook Pilea registers during connection listens for status changes on issues Pilea created. When one changes in Jira - for example, an issue gets closed - the corresponding Pilea backlog item updates to match. No manual bookkeeping, no stale backlog.

💡 Tip: This means “done” in Jira is “done” in Pilea. You can trust the backlog status when reporting back to customers who asked for something.

What Pilea does and doesn’t do

Does: list your projects, create an issue when you click export, and mirror status changes from Jira back to the Pilea item.
Doesn’t: read your existing Jira issues in bulk, or import them into Pilea as feedback. The read scope exists to list projects and track the issues Pilea created - not to crawl your Jira.

Troubleshooting

Status changes in Jira aren’t showing up in Pilea The webhook is registered at connection time. If mirroring stopped working, try disconnecting and reconnecting Jira from the Integrations page so the webhook is re-registered.

Next: Exporting backlog items to GitHub Issues

Exporting backlog items to Jira