Collect feedback
from Discord.

Turn a message from your Discord community into a feature request your team can track. Review the draft in Ducalis, organize related ideas and connect it to backlog work.
Capture a message Review the draft Organize Link to backlog
Apps → Create Idea Voice messages Thread confirmation Server authorization Draft before publishing Labels · duplicates Link to backlog Customer votes Public roadmap
// capture

Choose a Discord message and save it as a draft request.

// organize

Review duplicates, add labels and connect the request to product work.

// sample workflow

One Discord request, from message to backlog

A community member asks in #product-feedback: “Please add a dark theme.” Your team turns that message into one organized request.

  1. Capture: open the message’s More menu, choose Apps → Create Idea, and check the preview. Select the organization and voting board, click Continue, then Create Idea.
  2. Review the draft: the request appears in Ducalis as a draft. Check its meaning and add the customer context before publishing.
  3. Organize: add an appearance label, look for related requests and review any duplicates before merging them.
  4. Link to backlog: add the reviewed idea to your internal backlog or link it to an existing issue, such as APP-218.

Enable the creation-message option during setup to receive a confirmation in the Discord thread. The draft gives your team a place to preserve the member’s request and connect it to the work you review next.

Follow the Discord capture setup → 
┌─ LINKED PRODUCT WORK ────────┐
│  idea             Dark mode  │
│  issue              APP-218  │
├──────────────────────────────┤
│  Reviewed request → backlog  │
│  Customer context linked     │
│  Ready for prioritization    │
└──────────────────────────────┘
Sample request: Dark mode. Steps repeat while the example is visible.

Connect Discord, then capture the messages that matter

Authorize Ducalis for the server you choose. The message action lets your team decide which community messages become requests and which voting board receives them.

New to Ducalis?

Create your workspace

Already have an account?

Connect Discord

Need the steps?

Read the setup guide →
Choose the server and authorize the permissions shown during setup. The creation-message option controls whether a confirmation appears in Discord. See the Discord connection steps.
// review before publishing

Keep the request clear and organized

The draft gives your team a place to check the request before it reaches a public board. Edit the title and description, add labels and choose the appropriate board visibility.

Ducalis’s built-in AI chat or your own assistant through cloud MCP can help rewrite a public idea using your template and language. Review the result and check related ideas before deciding whether to merge them.

Keep bugs and feature requests distinct when they describe different problems, even if they mention the same feature.

See how to organize feature requests → 
┌─ REVIEW THE REQUEST ─────────┐
│  label           appearance  │
│  related idea    Dark theme  │
├──────────────────────────────┤
│  Find matching requests      │
│  Review matches, then merge  │
│  Preserve author and contex  │
└──────────────────────────────┘
Sample request: Dark mode. Steps repeat while the example is visible.
// product handoff

Connect the request to the backlog

Add the idea to your internal backlog or link it to an existing issue. Your team can evaluate it alongside other requests, bugs and planned work.

Connected tracker issues and configured status rules help keep the request aligned with delivery progress. Board subscribers can follow the request according to their notification settings.

Prioritize organized requests → · See the full feedback-to-release workflow →

Learn how ideas link to backlog issues → 
┌─ LINKED PRODUCT WORK ────────┐
│  idea             Dark mode  │
│  issue              APP-218  │
├──────────────────────────────┤
│  Reviewed request → backlog  │
│  Customer context linked     │
│  Ready for prioritization    │
└──────────────────────────────┘
Sample request: Dark mode. Steps repeat while the example is visible.

Give community feedback a shared place to review

// customer feedback

Capture a feature request from a beta tester or community member.

Capture a suggested feature, record the problem it would solve, and group it with related requests.

// team suggestions

Keep feature requests and bug reports clear for your team.

Capture useful messages from your community server. Keep bugs distinct when they need reproduction steps, and link reviewed requests to the right backlog issue.

Watch the Discord capture walkthrough

See how the message action opens request creation. The setup guide above covers server authorization, the message action and draft review.

Connect requests to the tools your team uses

Set up the tracker connection for your backlog. Availability and sync direction depend on the integration and plan.

Jira Cloud Jira Server Linear GitHub Asana ClickUp Trello YouTrack

Plan what happens after a Discord message

These board playbooks explain request organization and follow-up. Use the Discord setup guide above for the connection and message action.

Give Discord requests a place in your backlog

Create your workspace, connect Discord and capture one request for your team to review.

Start collecting requestsConnect Discord
┌─────────────────────┐
│  CAPTURE.           │
│  ORGANIZE.          │
│  LINK TO BACKLOG.   │
└─────────────────────┘