# Turn Customer Feedback into Linear Projects and Jira Epics Turn a ranked backlog opportunity into a Deck Project that keeps its customer evidence, then link it to one Linear project or Jira epic for delivery. - URL: https://getdeck.io/playbooks/opportunity-to-delivery - Author: Matt Teixeira - Published: 2026-11-01 - Updated: 2026-11-01 - Stage: Act ## How Do You Turn a Backlog Opportunity into Delivery Work? You create one Project from the opportunity so its customer evidence travels with it. Give the Project an owner, an overview in the customers' words, and success metrics. Then link it to one Linear project or Jira epic, so the team builds in their own tool while the evidence stays in Deck. ## Why Customer Evidence Gets Lost Between the Backlog and Linear The backlog says what customers want. The Linear ticket says “improve exports.” Somewhere between the two, the quotes, the customer count, and the reason it ranked high fall away. Engineers build from a title, and nobody can trace the work back to the people who asked. ## How Deck Keeps the Evidence on the Project In Deck, a Project created from an opportunity links back to it and starts with that opportunity's insight evidence. You add the owner, the overview, and the success metrics on the Project. Then you link one Linear project or Jira epic. Deck refreshes status and owner from Linear or Jira daily, while the overview, evidence, and success metrics stay in Deck. Deck features used: - [Opportunity Backlog](https://getdeck.io/product/opportunity-backlog) - [Projects](https://getdeck.io/product/projects) - [Integrations](https://getdeck.io/product/integrations) ## How to Turn an Opportunity into a Linear Project or Jira Epic in Deck ### 1. Pick the Opportunity Open Build → Opportunity Backlog and open a ranked opportunity. Check Related Work Items in its ⋯ menu first. If a Project already exists, continue with that one instead of creating a second. ### 2. Create the Project from It In the opportunity's ⋯ menu, choose Create Project. Give it a short outcome title, such as “Bulk export for admins,” and a one or two sentence description. Deck links the Project back to the opportunity and seeds it with the opportunity's insight evidence. ### 3. Set the Owner and Dates Open the Project from Build → Projects. Fill in the owner, and set the status and target date in the Project header. Only use a target date the team agreed. ### 4. Write the Overview and Success Metrics On the Overview tab, write the problem in the customers' words with two or three quotes from the Evidence tab, plus what is in and out of scope. On Success Metrics, write what must change in the feedback after release, such as fewer negative insights in the linked theme. ### 5. Link Linear or Jira Open the Project's external handoff menu. Link an existing Linear project or Jira epic, or create a new one from the Project. Linear or Jira must first be connected in Settings → Integrations by an org admin. ### 6. Check the Handoff Confirm the Project shows its evidence, the overview, the success metrics, and one external link. Back on the opportunity, Related Work Items now lists the Project. ## Hand Off an Opportunity with Your AI Agent You need: - Deck MCP connected to your agent - Customer feedback already in Deck Your agent starts with the `explore_opportunity_backlog` tool. Paste this prompt into your agent: ```text Use Deck MCP. Fetch and follow https://docs.getdeck.io/docs/agents/workflows/opportunity-to-delivery.md ``` Full agent workflow: https://docs.getdeck.io/docs/agents/workflows/opportunity-to-delivery.md ## Project Handoff Template ### Project Handoff Brief ```text ## Project Title: [Short outcome, e.g. Bulk export for admins] Opportunity: [Opportunity name] ([Deck impact score], [Deck count] insights) Owner: [Name or none] Initiative: [Initiative or none] Target date: [Only a date the team agreed] ## Overview Problem: [One or two sentences in the customers' words] Quote: "[Customer quote 1]" Quote: "[Customer quote 2]" In scope: [What ships] Out of scope: [What does not] ## Success metrics - [What must change in the feedback after release, e.g. fewer negative insights in [Theme]] ## Handoff [ ] Evidence is attached to the Project [ ] Linked to one Linear project or Jira epic: [URL] [ ] The opportunity lists the Project in Related Work Items ``` ## Frequently Asked Questions ### Does Deck create the Linear project or Jira epic? It can, from the Project's external handoff menu in the web app. Deck MCP tools only link an item that already exists. Linking reads the item and stores its title and key. Nothing changes in Linear or Jira. ### Who can connect Linear or Jira? Only org admins, in Settings → Integrations. Linear and Jira do not count toward the Free plan's one-integration limit. ### Can one Project link to several Linear or Jira items? No. A Project has one external link at a time, and a new link replaces the old one. A Linear project or Jira epic can link to only one Deck Project. Unlinking removes only the link in Deck. ### What syncs back from Linear or Jira? Deck refreshes top-level details daily, such as status, owner, and the linked title. The overview, evidence, and success metrics stay in Deck and are never overwritten. Jira start and target dates do not sync. ### Does this use credits? Asking Deck AI to rewrite the Project's Evidence story spends credits and replaces that section. Your agent asks for an explicit yes every time before it does that. ### Can my AI agent run this? Yes. With Deck MCP connected, paste the prompt on this page. The agent shows you a draft Project first and asks before it creates anything. It writes to the Project only and never changes the opportunity. ## Related Playbooks - [Plan a Product Initiative from Your Opportunity Backlog](https://getdeck.io/playbooks/plan-initiative.md): Group two to six backlog opportunities that share one customer problem into a Deck initiative with a clear goal, linked evidence, and written outcomes. - [Build Features from Customer Evidence, Not Guesswork](https://getdeck.io/playbooks/build-from-evidence.md): Turn a Deck Project into a shipped change where every requirement links to the customer insights behind it. Build it yourself or with your coding agent. - [Prioritize Your Product Backlog with Customer Evidence](https://getdeck.io/playbooks/prioritize-backlog.md): Pick the top opportunities from a backlog ranked on customer evidence, with a reason, a risk, and quotes for each pick. Run it in Deck or with your AI agent.