Prioritize your Jira backlog
with customer feedback.

Connect customer requests to Jira Cloud issues, evaluate the work in Ducalis and put priority results back in Jira. Keep your public roadmap connected to the tasks your team is delivering.
Import backlog RICE · WSJF Two-way sync Customer feedback
JQL · saved filters Sub-tasks with parents Custom fields Existing field mapping Backlog · Active sprints Sprint-end schedule Sync-In Conditions Push issues RICE · WSJF Customer votes Linked public idea
// customer context

Give Jira issues the context behind the request.

Link reviewed feedback to the work it describes so your team can evaluate the customer problem alongside implementation effort.

// shared priorities

Keep the result visible where work happens.

Map selected scores and rankings to Jira custom fields, then configure statuses for the linked public idea.

// illustrative Jira Cloud workflow

From a feature request to Jira backlog priorities

A customer asks for Custom roles. Your team reviews the request and connects it to Jira issue PROD-142.

  1. Review the feedback: record the customer problem and group related requests before linking them to work.
  2. Import and link: select Jira issues using filters and preview. In the idea card, choose Link and find the existing issue, or create new work through the connected tracker.
  3. Prioritize: score the issue with impact, effort and customer context, and review the result with your team.
  4. Return priorities to Jira: send chosen results to suitable Jira custom fields through configured Sync Back.
  5. Show delivery progress: status rules update the linked roadmap idea when the issue progresses.

The example returns score 300 and rank #2 to the selected custom fields. Your team chooses which work goes into the plan.

Connect Jira Cloud and follow the setup → 
┌─ 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 request, issue PROD-142, score and rank. Import, idea linking, Sync Back and roadmap status rules are separate configured steps.

Import the Jira issues your team wants to evaluate

Connect Jira Cloud and select work using a saved Jira filter, JQL or Ducalis filters. Review the matching issues before starting the import.

Choose projects, issue types and scope

Use the filter options that match your backlog. Jira sub-tasks can be imported with parent tasks when selected in the import conditions.

Configure Jira import filters →

Adjust the scope as priorities change

Edit Sync-In Conditions to change which issues belong in the Ducalis board. Check the selected scope before expanding the workflow.

Edit filters and review the import →
// RICE · WSJF · custom criteria

Prioritize Jira tasks with impact, effort and customer context

Use RICE, WSJF or a custom framework to evaluate Jira work. Define consistent criteria and units, then have the people with relevant expertise score the issues.

In the example, Custom roles competes with SSO, an export fix and other Jira backlog work. Votes and customer context help explain the demand; engineering estimates the effort.

When engineering revises effort from 4 to 6 person-months, the example RICE score falls from 60 to 40 and its custom total from 320 to 300. Your team reviews the trade-offs and chooses what to build.

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

Set up 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 2 points per vote and 1 point per $1k of associated customer ARR to RICE. These weights are illustrative; associated ARR is context, not predicted new revenue.
// Ducalis results → Jira custom fields

Sync priority results back to Jira Cloud

Choose the outputs your team needs: total scores, priority rankings, criterion scores, score statuses, percentages or idea votes. Map them to suitable Jira custom fields.

  1. Choose the Ducalis fields to send.
  2. Create suitable Jira custom fields, or configure existing ones, and add them to the relevant board views.
  3. Activate Sync Back in Ducalis.
  4. Configure delivery by sprint end or selected days and times, or run Manual Sync Back to test immediately.

After syncing, the chosen fields can show the results in your Jira backlog, active sprints and issue cards. Check a sample issue before expanding the setup.

Compare the general tracker-sync workflow →

Configure Jira custom fields and Sync Back → 
┌─ JIRA CLOUD SYNC BACK ─────────┐
│  custom score field       300  │
│  custom rank field         #2  │
├────────────────────────────────┤
│  Map selected Ducalis data     │
│  Activate Sync Back            │
│  Scheduled or manual sync      │
└────────────────────────────────┘
Illustrative Jira Cloud setup, issue ID, score and rank.
// Jira status → linked public idea

Keep your public roadmap aligned with Jira progress

Configure rules for the linked idea, such as Jira In progress → idea In progress. The public roadmap then shows the status of work your customers asked for.

If Done precedes the production release, add the documented release-webhook condition. Jira’s Resolution field can also distinguish completed work from cancelled or postponed issues.

Your team chooses the public summaries and audience. After release, review and approve the announcement before publishing it in the changelog and widget.

Share your public roadmap → · Publish reviewed release updates →

Configure Jira-to-idea status rules →
Review suggestions

Edit boards offline

Team-selected idea → Planned, related requests linked

PROD-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 a small Jira prioritization workflow

Verify the Jira connection, selected issues, scoring criteria, destination fields and linked-idea status rule. Available fields and permissions depend on your setup.

Using Jira Server? → · See other tracker workflows →

Prepare and prioritize Jira work

These resources cover backlog preparation and scoring. Use the Jira setup steps above for connection and sync settings.

Give your Jira backlog a clear product priority.

Import a small set of issues, link one customer request, score the work and test how results and statuses reach Jira and your roadmap.

Prioritize your Jira backlog

Follow the Jira Cloud setup →