On this page
Send to Jira
Send to Jira turns a work item into a Jira issue that links back to it. 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.
Send to Jira… shows in the menu before you connect. Until you do, its dialog asks you to connect, and Open Connectors takes you there.
If you connected Jira before Send to Jira was available, reconnect it once in Settings → Connectors. Until you do, Jira refuses the send and the dialog says so.
Anyone who can create work items can send them: owners, admins and editors.
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.
Send it
Click Send. The issue key appears on the work item's row and in its details, linked to Jira.
The issue's summary is the work item's name. Its description holds the work item's summary and instructions, formatting included, and a link back to the board. A Fix becomes a Bug and every other type a Task; when a project doesn't use those names, we use its first standard type.
A work item is sent once, and Send to Jira… then leaves its menu.
Send an epic
Open the epic's menu on the work items screen and choose Send epic to Jira…. We create an Epic in Jira, then each of its work items as an issue under it.
Sending the epic again creates only the work items added since, under the same Epic. If Jira stops part-way, the issues already created stay linked and the next send picks up where it stopped. A work item sent 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 as Completed, Declined or Resolved, the Jira issue gets a comment saying how and by whom. The comment carries the note, commit and pull request if there are any.
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, the issue key on the work item shows a caution mark and its details say why.
Bring an epic in from Jira
In Chat, paste a Jira epic's link or name it: "draft work items from PAY-120". ProvenMap reads the epic and its child issues with your Jira account, finds the boards and nodes each concerns, and asks you to confirm before drafting the work items.
What's next
Last updated October 24, 2026