Connecting integrations

Connect a source system and changelog entries appear automatically when you ship. Four supported sources, each with its own permission model.

GitHub Releases

Best fit for teams that already use the Releases tab on GitHub. Every published GitHub Release becomes a changelog entry, with the release notes as the body and the tag name in the title.

• Connect at /admin/<your-slug>/integrations → GitHub.
• OAuth scopes are read-only (repo:status, public_repo, read:org).
• Pick the repository to sync (format owner/repo).
• Click Sync now after creating a new Release.

JIRA Cloud

If your team works in JIRA, point Drumroll at a project and we'll turn fix versions into changelog entries, with their associated issues listed in the body.

• OAuth scope is read:jira-work only.
• Issues' fix version becomes the entry title and date.
• Issue types map to section headings: stories → New features, improvements → Enhancements, bugs → Bug fixes.

Bitbucket Cloud

For teams shipping from Bitbucket, every annotated tag becomes a changelog entry.

• OAuth scope is repository read.
• The tag name is the entry title; the tag message is the body.
• Rate-limited responses are retried with backoff so large syncs complete reliably.

Markdown repo

The most flexible option. Point Drumroll at a folder in a GitHub or Bitbucket repo (e.g. docs/releases/) and every .md file becomes a changelog entry or guide, with frontmatter for title, slug, date, tags, and status.

---
title: v1.2 launch
date: 2026-05-12
tags: [release, public]
status: published
---

# What shipped

- New search across guides
- Tags on guides

Synced guides are read-only inside the editor - edit the source file and re-sync to update.

Removing an integration

Disconnect any integration any time from the integrations page. Access tokens are deleted immediately. Already-synced entries stay - they're now manual entries you can edit or delete.