Last updated September 25, 2026
Send to Jira
Send to Jira turns a work item into a Jira issue that links back to it, so the work your team tracks in Jira stays tied to the board. The work item shows the issue key. When the work item closes, the issue gets a comment saying how.
Send to Jira is on every plan.
Before you start
Connect your own Jira account in Settings → Connectors. Jira is a personal connection: we create issues under your account, so Jira's own permissions decide which projects you can send to. See Integrations Reference.
If you connected Jira before Send to Jira was available, reconnect it once in Settings → Connectors. Reconnecting grants the permission to create issues. Until you do, Jira refuses the send and the dialog says so.
Anyone who can create work items can send them: owners, admins and contributors.
Send a work item
Open Send to Jira
On the work items screen, open the work item's row menu and choose Send to Jira….
Choose where it goes
Pick the project. If your Jira account reaches more than one Atlassian site, pick the site first. We remember both for this workspace, so next time the dialog opens on them.
Send it
Click Send. The issue key appears on the work item's row and in its details. Click it to open the issue in Jira.
The issue takes the work item's name as its summary. Its description holds the work item's summary and instructions, plus a link back to the work item on the board. Their formatting carries over: headings, bulleted and numbered lists, bold, italics, code and links read in Jira as they do on the board. A Fix becomes a Bug, and every other type becomes a Task. When a project doesn't use those names, we use the project's first standard type.
A work item is sent once. After that, Send to Jira… disappears from its menu.
Send an epic
Open the epic's menu on the work items screen and choose Send epic to Jira…. We create the epic as an Epic in Jira, then each of its work items as an issue under it.
You can send an epic again later. The second send creates only the work items added since, under the same Epic, and never sends a work item twice. If Jira stops part-way, the issues already created stay linked, and the next send picks up where it stopped.
A work item you send on its own after its epic is in Jira also goes under that Epic.
When the work item closes
When a sent work item closes, the Jira issue gets a comment saying how it closed and who closed it. The comment carries the note, commit and pull request if there are any. That covers every way a work item closes: Completed (by a developer, by Mark completed, or by a sync that finds the change already in the code), Declined, and Resolved.
The comment is posted from the Jira account of whoever sent the work item, even when a developer's plugin closed it. If that person has since disconnected Jira, or Jira refuses the comment, we don't post it. Instead, the issue key on the work item shows a caution mark, and the work item's details say why.
Bring an epic in from Jira
Chat can also turn a Jira epic into work items. Paste the epic's link in Chat, or name it: "draft work items from PAY-120". Chat reads the epic and its child issues with your Jira account and finds the boards and nodes each one concerns. It asks you to confirm before it drafts the work items.