Jira Integration

Connect Jira when your team plans delivery in Jira but wants Projects in Deck to stay grounded in customer evidence.

With Jira connected, Deck can import Jira Epics into Projects, link existing Projects to Jira Epics, and create Jira Epics from Deck Project context.

What You Can Do

import an existing Jira Epic as a Deck Project
link an existing Deck Project to a Jira Epic
create a new Jira Epic from a Deck Project
choose Jira Projects, workflow statuses, and assignable users during handoff
keep the Deck Project connected to the Jira Epic URL and top-level status metadata

Deck uses Jira Projects as containers for Epics. Deck Projects link to Jira Epics, not Jira Projects.

Connect Jira

Go to Settings -> Integrations.
Open the Jira integration.
Click Connect.
Complete the Atlassian authorization flow.
Return to Deck and open Build -> Projects.

After connecting, Jira options appear in Project import and external handoff menus.

Import a Jira Epic

Open Build -> Projects.
Choose the Jira import option.
Select a Jira Epic.
Optionally choose the initiative the Project should belong to.
If segments are enabled, optionally choose the segment for the Project.
Confirm the import.

Deck creates a new Project and copies mappable fields such as the title, description, status, owner, and Overview content when available.

Link an Existing Deck Project

Open the Deck Project.
Open the external handoff menu.
Choose the Jira link option.
Select a Jira Epic.
Link the Project.

Deck stores the Jira Epic link and fills only empty execution metadata from Jira. If the Deck Project is still Not started, Deck can update its status from the Jira status category. Deck does not overwrite the Project title, owner, description, segments, Overview, Evidence, or Success Metrics during linking.

Create a Jira Epic From Deck

Open a Deck Project.
Open the external handoff menu.
Choose the Jira create option.
Select the Jira Project that should contain the Epic.
Choose available owner, priority, and status details.
Optionally generate an editable AI overview from the Deck Project context.
Create the Epic.

Deck then stores the Jira Epic link on the Project.

Important Behavior

A Deck Project can have one external execution link at a time.
A Jira Epic can be linked to one Deck Project per organization.
Unlinking removes only the Deck-side link. It does not delete or change the Jira Epic.
Linking an existing Deck Project fills only empty or default execution fields from Jira. Jira start and target dates are not filled because Jira date fields are customer-specific.
Deck refreshes provider-owned top-level Project metadata daily, including title, description, owner, status, completion time, and the linked Jira URL/title.
Deck does not sync Jira start or target dates because Jira date fields are customer-specific. Project documents, evidence, and generated sections remain Deck-owned and are not overwritten by Jira sync.

Jira