A changelog that follows
your fix versions.
Authorize once, pick a project, hit sync. Drumroll lists every fix version, fetches the issues attached to each, and turns them into changelog entries grouped by issue type.
How it works
Three steps,
under five minutes.
- 01
Authorize JIRA
Standard Atlassian OAuth 2.0 (3LO). Read-only scopes (read:jira-work + offline_access). Tokens are AES-256 encrypted before they touch our database; refresh tokens keep syncs working past the 1-hour access-token expiry without forcing you to reconnect.
- 02
Pick a project
Drumroll lists every Atlassian project your account can see. Choose one - the project key gets stored on the workspace, not your user.
- 03
Sync on demand
Click Sync. Every fix version becomes one changelog entry, with the issues grouped by type (Story, Bug, Task, etc.). Re-syncs update entries in place.
What syncs
Capabilities & limits.
We’re explicit about what JIRA Cloud sync handles and what it doesn’t. Most teams find the first list covers their actual use; the second is the part vendors usually hide.
Supported
- JIRA Cloud OAuth 2.0 (3LO)
- All fix versions on a project, released or unreleased
- Issues grouped by issue type with status indicators
- Stable source-ref dedupe - re-syncs update existing entries, never duplicate
- Released versions auto-publish; unreleased become drafts
- Per-version error isolation - one bad fix version doesn't fail the whole run
Not yet supported
- JIRA Server / Data Center (on-premise) - Cloud only for v1
- Real-time webhooks - sync is on-demand by design
- Custom JQL - we filter by fixVersion exactly
Try it on a real project.
Two minutes to sign up, one click to connect, your team’s shipping rhythm becomes a public page. Always free.
Create a workspace