Prioritize your Linear backlog
with customer feedback.

Connect customer requests to Linear issues, score the work in Ducalis and configure priority Sync Back with your AI assistant. Keep roadmap progress connected to the tasks your team delivers.
Import backlog RICE · WSJF Two-way sync Customer feedback
Issues · Projects Real-time project sync AI-assisted setup Priority field mapping Agents · schedule Private-team webhook Sync-In Conditions Push issues RICE · WSJF Customer votes Linked public idea
// customer context

Keep the request connected to Linear work.

Link reviewed customer feedback to the issue that addresses it, and use that context when evaluating the backlog.

// assistant-assisted sync

Configure how results return to Linear.

Choose the source, destination and schedule with the assistant, then review the configuration and test it on selected work.

// illustrative Linear workflow

From customer feedback to Linear backlog priorities

A customer asks for Custom roles. Your team reviews the request, links it to Linear ENG-142 and compares the work with other issues.

  1. Review the request: capture the customer problem and organize related feedback.
  2. Import and link: connect Linear, select Issues and filters, then link the idea to its existing issue or create new work.
  3. Prioritize in Ducalis: score impact, effort and customer context, then review the result with your team.
  4. Set up Sync Back: use the assistant to choose the data, target field and schedule. Review, confirm and test the configuration.
  5. Update progress: configured rules keep the linked public idea aligned with the issue’s status.

The example’s score 300 and rank #2 are prioritization results in Ducalis. The assistant helps configure how selected data returns to a supported Linear field.

Connect Linear and import selected issues → 
┌─ LINKED PUBLIC IDEA ───────────┐
│  tracker issue        ENG-142  │
│  idea            Custom roles  │
├────────────────────────────────┤
│  In progress → Done            │
│  Configured status rule        │
│  Roadmap status updated        │
│  Check production release      │
└────────────────────────────────┘
Illustrative Linear setup, issue ID, score and rank.
Sample request, ENG-142, scores and rank. Import, idea linking, Sync Back and roadmap status rules are separately configured. Destination fields receive the mapping your team has reviewed.
// RICE · WSJF · custom criteria

Prioritize Linear tasks with impact, effort and customer context

Evaluate Linear work using RICE, WSJF or the criteria your team chooses. Define consistent units and have the relevant teammates contribute their estimates.

In the sample, Custom roles competes with SSO, an export fix and other Linear backlog work. Customer votes and associated account context help explain the demand; engineering reviews implementation effort.

Changing effort from 4 to 6 person-months brings the example RICE score from 60 to 40 and its custom total from 320 to 300. Your team reviews the trade-offs, dependencies and capacity before deciding what goes into the plan.

RICE scoring → · WSJF prioritization → · Review the scoring workflow →

Configure criteria and team scoring →
  1. SSO request
    R250 I2 C80% E4
    100
  2. Fix export crash
    R400 I1 C80% E4
    80
  3. Custom roles
    R150 I2 C80% E4
    60
  4. API refactor
    R200 I1 C80% E4
    40
Synthetic data. Reach is people per quarter; effort is person-months; confidence is 80%. The custom example adds illustrative votes/associated ARR weights to RICE. Associated ARR is customer context, not a forecast of new revenue.
// AI assistant → reviewed Sync Back job

Return priorities to Linear through your AI assistant

Open the built-in Ducalis AI chat, or ask your connected assistant through cloud MCP, to set up Sync Back to Linear. It asks for the details needed to configure the job.

  1. Connect: authorize Linear if the connection is not already in place.
  2. Choose the source: specify the Ducalis criterion or field you want to send.
  3. Choose the destination: select a supported Linear field and review the mapping, including how results should map to Priority when that is your target.
  4. Choose the timing: set the schedule and confirm the relevant time zone.
  5. Review and test: inspect the preview, confirm the setup and run a test on selected work.
  6. Manage the job: monitor progress on Agents; ask the assistant to change the schedule or use Agents to run, pause or delete the job.
Follow the AI-assisted Linear Sync Back setup → 
┌─ TEST AND MONITOR ─────────────┐
│  test issue           ENG-142  │
│  Check destination in Linear   │
├────────────────────────────────┤
│  Monitor on Agents page        │
│  Run · pause · edit schedule   │
└────────────────────────────────┘
Illustrative AI-assisted setup, field mapping, schedule and test issue.

How Ducalis scoring works with Linear Priority

Linear’s native issue Priority expresses urgency using No priority, Low, Medium, High or Urgent. Ducalis lets your team inspect the scoring and customer evidence behind a product decision.

Use a reviewed mapping for the destination

The sample score 300 is a custom result in Ducalis. When targeting Linear Priority, review how the selected data should translate to the field’s supported values before confirming Sync Back.

Configure the field and preview →

Keep the detailed rationale accessible

Teammates can review the scored backlog in Ducalis. The integration guide also describes sharing the backlog, viewer access and CSV export.

Share results with your team →

Read Linear’s native Priority documentation → · Compare tracker-sync workflows →

// Linear status → linked public idea

Keep your public roadmap aligned with Linear progress

Link the public idea to the relevant Linear issue and configure status rules, such as In progress → In progress and released work → Done.

If the issue reaches Done before the feature is available to customers, use the documented production-release webhook condition. Your team chooses the public summaries and audience.

After release, review and approve the announcement before publishing it on the changelog and in-product widget.

Share your public roadmap → · Close the loop with release updates →

Configure issue-to-idea status rules →
Review suggestions

Edit boards offline

Team-selected idea → Planned, related requests linked

ENG-142linked backlog issue

Custom roles

Done

Configured status rule → Done on the roadmap

Public Roadmap PublicSelected customersTeam only
Roadmap25Bugs10Enterprise6

Planned

  1. ▲ 4 Offline editing Mobile +3 similar requests Shipped

In progress

  1. ▲ 19 Dark mode UI Shipped
  2. ▲ 31 SSO login Security Shipped

Done

  1. ▲ 40 Custom roles Permissions Shipped
  2. ▲ 42 CSV export Reporting Shipped

Check the setup for the Linear work you use

Configure private-team updates

Private Linear teams have a documented webhook setup for real-time issue updates. Follow that guide when your imported work belongs to a private team.

Set up private-team webhooks →

Check other entity levels separately

This workflow focuses on issues. Projects and initiatives have their own documented sync limitations; check the guide before extending your setup.

Review projects and initiatives →

Explore feedback-to-Linear workflows

Follow concrete request scenarios and prepare the context your team needs before reviewing Linear priorities.

Give your Linear backlog a clear product priority.

Link one request, score a small issue set and review a test Sync Back job with your assistant before expanding the setup.

Prioritize your Linear backlog

Follow the Linear connection steps →