Exporting backlog items to Jira

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

1. In Pilea, go to Integrations in the sidebar under Data Sources.
2. Find Jira in the grid and click Connect.
3. Click Connect in the dialog. You’ll be redirected to Jira to authorize access.
4. Approve the requested scopes - read:jira-work, write:jira-work, manage:jira-webhook and offline_access. The webhook scope is what powers the status mirroring.
5. 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

1. Open the backlog item and go to its Details tab.
2. Under Export to Issue Tracker, click Export to Jira.
3. Pilea lists your Jira projects - pick where the issue should go.
4. 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. A Remove link button detaches the item from the issue if you need to export again.

How the two-way status sync works

The first time you export to a Jira project, Pilea registers a webhook on your Jira site that listens for updates to issues in that project. Each new project you export to is added to it. When an issue Pilea created changes status, the Pilea backlog item updates to match:

Jira status	Pilea status
To Do	Ready for dev
In Progress	In progress
In Review	Ready for test
Done	Completed

Other Jira statuses are ignored. Jira expires these webhooks after 30 days, so Pilea refreshes them weekly and re-registers any that have gone missing. You don’t need to do anything to keep mirroring alive.

💡 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 Check the issue’s status is one of the four in the table above; others don’t map to a Pilea status. If mirroring has stopped entirely, the webhook is checked and re-registered automatically once a week. To force it sooner, export another item to the same project, or disconnect and reconnect Jira from the Integrations page.

Next: Exporting backlog items to GitHub Issues