Automate release notes.
Keep customers in the loop.

Turn completed work from Jira, Linear and other trackers into clear product updates. AI drafts the announcement, your team reviews it, and your changelog widget brings it into your product.

Draft your first release note

See completed work become an update →

// automate

Connected work becomes a customer-facing draft.

Use linked ideas, status rules and AI announcements to keep release updates connected to what your team ships.

// review & publish

Your team approves what customers see.

Check the wording and availability, approve the announcement and show it in your in-product changelog.

// sample release · Jira + Linear

Two completed tasks. One clear product update.

Your team ships CSV invoice export in Jira and fixes the export button in Linear. Both issues are linked to the corresponding ideas in Ducalis.

  1. Sync completion: configured status rules update the linked ideas when the issues reach the completion statuses you chose.
  2. Generate drafts: with AI announcements enabled, moving an idea to Done creates an announcement draft. You can also prepare it before the release.
  3. Review and approve: check what shipped, rewrite the wording where needed and approve each announcement.
  4. Publish in your product: approved announcements for Done ideas appear on the changelog, which your embedded widget displays to customers.

The customer sees “Export invoices as CSV” and “Your export button is back,” with an explanation of where to use them.

app.acme.com
Illustrative release · sample issue IDs.
// connected trackers · status rules

Connect Jira, Linear and the work you want to announce

Connect Jira Cloud, Jira Server, Linear or another supported tracker. Link the relevant backlog issues to customer-facing ideas in Ducalis, then map tracker statuses to idea statuses.

For example, Jira’s Done and Linear’s completed status can move their linked ideas to Done. Choose the statuses that match your delivery process.

If work reaches Done before it is available to customers, add the documented release-webhook condition. For Jira, a resolution rule can distinguish a shipped change from a cancelled issue.

Other connections include Asana, ClickUp, Trello, YouTrack and GitHub.

┌─ AI ANNOUNCEMENT DRAFTS ───────┐
│  Export invoices as CSV        │
│  Download invoices in Billing  │
├────────────────────────────────┤
│  Your export button is back    │
│  Export with active filters    │
├────────────────────────────────┤
│  Draft · not published         │
└────────────────────────────────┘
Illustrative release · sample issue IDs.
Connector availability and sync direction depend on the integration and plan. Choose which linked ideas should receive announcements in your board’s automation settings.
// AI draft · human review

Turn technical work into release notes customers understand

AI prepares an announcement from the idea’s context. Review the title and description, save the draft or ask AI to rewrite it, then approve the announcement.

  • Explain the benefit: “Download invoices from Billing to share with your accountant.”
  • Make it actionable: say where to find the change and include useful links.
  • Check the release: verify availability, audience and any limitations before announcing.
  • Keep internal details private: remove internal discussions, issue IDs and sensitive context from the customer-facing text.

Prepare announcements while the feature is in development, or review the draft generated when its idea moves to Done. Approval controls what reaches your changelog.

┌─ REVIEW BEFORE PUBLISHING ─────┐
│  Confirm features are live     │
│  Check benefit and wording     │
│  Remove internal details       │
│  Check audience and links      │
├────────────────────────────────┤
│  Save or rewrite the draft     │
│  Approve announcement          │
└────────────────────────────────┘
Illustrative release · sample issue IDs.
// approved updates · in-product widget

Publish the update where customers use your product

Install the Ducalis widget in your web product and enable its changelog section. Customers can read approved release announcements while using your app.

The same announcements can appear on your dedicated changelog page. Link the release back to the original request so customers can follow the work they asked for.

In the example, the widget shows the CSV export announcement and the export-button fix after your team has checked and approved both drafts.

Read the Ducalis changelog → · Connect updates to your public roadmap →

app.acme.com
Illustrative release · sample issue IDs.

Keep each release consistent, from announcement to delivery

Set up the format and delivery once, then review the customer-facing details of each release.

// template

Use a repeatable release-note format

Choose the blocks and announcement detail your release notes include. Group updates into a readable digest.

Configure a template →
// delivery

Schedule subscriber emails

Send a release-note digest manually, on a recurring schedule or using a configured release webhook. Email timing is configured separately from changelog publication.

Set up delivery →
// audience

Make the changelog fit your product

Configure the widget’s appearance, display sections and voter identification. Choose your board’s visibility and indexing settings for your audience.

Configure your widget →

From customer request to shipped update

Changelog automation closes the loop. Ducalis also helps your team collect requests, organize them and decide what to build next.

Collect and organize requests

Give feedback a clear home before it reaches your backlog.

Manage feature requests →

Choose what ships next

Evaluate customer requests alongside bugs and planned work.

Prioritize your backlog →

Follow the whole workflow

Connect feedback, requirements, priorities, delivery and customer updates.

From feedback to release →

Configure delivery for your audience

Practical guides for your release-note page, its audience and its presentation.

Branding and appearance

Choose the logo, theme and presentation for your public board and changelog.

Read the changelog guide →

Your domain

Review the documented custom-domain setup for your voting board and public updates.

Custom-domain setup →

Audience and access

Choose who can see your board and updates. Check visibility and voter settings for your intended audience.

Audience settings →

Localized updates

Use the step-by-step workflow for organizing release announcements in different languages.

Read the localization workflow →

Tracking setup

Check your board settings and confirm that your configured analytics measures the events your team needs.

Board configuration →

Release-note examples

Explore the original product reviews and practical lessons for writing updates customers can use.

Changelog writing tips →

Browse all changelog examples →

Learn how to write and deliver release notes

Combine a repeatable workflow with writing guidance and an independent in-app changelog review.

Ship the work. Share the value.

Connect one completed issue, review its announcement and publish your first update in a test widget.

Draft your first release note

Follow the release-notes setup →