Prioritize in Ducalis.
Keep Jira and Linear in sync.

Bring tracker issues into Ducalis, evaluate them with your team and send priority results back. Keep customer-facing roadmap statuses connected to the work your team is delivering.

Connect your task tracker

See issues become shared priorities →

// sync in

Evaluate the work already in your tracker.

Import selected Jira or Linear issues and keep customer requests connected to the backlog work you score.

// sync back

Put the results where your team works.

Configure the data, destination fields and schedule for your connector, then test how the results appear in your tracker.

// illustrative Jira Cloud workflow

Two-way task tracker sync, from issue to roadmap

Your team has a Custom roles issue in Jira Cloud. Import it into Ducalis, link the customer request and evaluate it alongside other backlog work.

  1. Import selected issues: authorize the connection, choose filters and review the matching work.
  2. Prioritize in Ducalis: score impact, effort and customer context, then review the ranking with your team.
  3. Sync results back: map the chosen results to Jira custom fields, activate Sync Back and choose scheduled or manual delivery.
  4. Update the public idea: link the issue to its roadmap idea and configure rules that translate tracker progress into idea statuses.

In the example, the selected Jira custom fields show a score of 300 and rank #2. The roadmap status follows a separate rule for the linked idea.

Set up Jira Sync Back → 
┌─ LINKED PUBLIC IDEA ───────────┐
│  tracker issue       PROD-142  │
│  idea            Custom roles  │
├────────────────────────────────┤
│  In progress → Done            │
│  Configured status rule        │
│  Roadmap status updated        │
│  Check production release      │
└────────────────────────────────┘
Illustrative Jira Cloud setup, issue ID, score and rank.
Sample issue PROD-142, scores and fields. Jira and Linear below show alternative connector setups for the same example request. Sync In, Sync Back and roadmap status rules are configured separately.

Choose which Jira and Linear issues enter Ducalis

Start with the work you want to evaluate. Review the import preview and adjust the selection as your backlog changes.

Jira: saved filters, JQL or Ducalis filters

Select issues by the projects and conditions relevant to your team. Use the documented filter options to control what enters the board.

Import Jira issues with filters →

Linear: select issues and filters

Connect Linear, select Issues and apply filters before importing. Edit Sync-In Conditions to change which issues belong on the board.

Connect and import Linear issues →

Keep customer requests linked

Add a reviewed idea to your internal backlog or link it to an imported issue. Customer context can inform scoring without copying your whole tracker into a public board.

Organize feature requests →

Using Azure DevOps, GitLab, Notion, monday.com or another tracker without a native integration? Import the backlog from a CSV file. See all task trackers →

// shared criteria · customer evidence

Give imported tasks priorities your team can explain

Evaluate tracker work with the same criteria as customer requests and other planned improvements. Use RICE, WSJF or custom scoring, then review uncertain inputs and team disagreements.

The sample Custom roles request has votes and associated customer context. Engineering reviews effort from 4 to 6 person-months, bringing the example custom score from 320 to 300.

Choose which result belongs in your tracker: a total score, rank or individual criterion supported by the connector. Your team decides what to build after reviewing the results.

Explore feedback and backlog prioritization →
  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 scoring example: reach is people per quarter; effort is person-months. RICE is extended here with illustrative votes/ARR weights. Associated customer ARR is context, not predicted new revenue. See /prioritization for the complete calculation.

Send prioritization results back to Jira Cloud

Choose the Ducalis results and the Jira custom fields that should receive them. Display those fields in the views your team uses for planning.

Map the data you need

Jira Sync Back supports total scores, priority rankings, criterion scores, score statuses, percentages and idea votes. Select the outputs useful to your team.

Choose Sync Back fields →

Configure suitable custom fields

Create fields or map existing suitable fields, then add them to the relevant Jira board views so the results are visible.

Set up Jira custom fields →

Activate, schedule and test

Enable Sync Back and configure delivery by sprint end or selected days and times. Run Manual Sync Back when you want to check the results immediately.

Configure and test delivery →
// Linear · assistant-assisted setup

Configure Linear Sync Back with your AI assistant

Open the built-in Ducalis AI chat, or ask your assistant through cloud MCP, to set up back sync to Linear. Authorize the connection if needed, then specify the Ducalis criterion or result, the destination field and the schedule.

Review the configuration preview before confirming it. Test the job, inspect its progress on the Agents page, and adjust or pause the schedule when needed.

When the target is Linear’s Priority field, review how the selected result should map to that field’s supported values. The Jira custom-field example above is a separate setup.

In this alternative example, Custom roles is the linked Linear issue ENG-142. The assistant helps configure Sync Back for the fields and timing your team chooses.

Follow the Linear Sync Back guide → 
┌─ 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.
// linked issue → public idea status

Keep roadmap progress aligned with delivery

Link the customer-facing idea to the relevant tracker issue. Configure status rules, for example In progress → In progress and completed work → Done.

If tracker Done happens before the feature reaches customers, use the documented production-release webhook condition. Your team chooses the ideas and details that are visible publicly.

Priority Sync Back sends scoring results to the tracker; status automation brings tracker progress to the linked idea. After release, reviewed announcements can close the loop with customers.

Build a public roadmap → · Automate release updates →

Configure roadmap 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

Start with the connector your team uses

Available fields, permissions, sync directions and timing depend on the connector and your setup. Follow its guide and verify a selected issue before expanding the workflow.

Jira Cloud integration → · Linear integration → · Other supported trackers → · Plans →

Explore the handoff to tracker work

Use these scenarios to understand the process around a tracker connection, from the source request to delivery updates.

Connect the backlog to the product decision.

Import a small set of issues, review their priorities, test Sync Back and verify one linked idea’s roadmap status.

Connect your task tracker

Follow your connector’s setup →