Released

The release notes generator reads completed issues in a version or sprint and writes a first draft in your format. You keep control of the headline features, so the polished paragraph is yours and the routine items are handled. Every draft lands as editable text, which matters because AI copy about internal refactors rarely reads well to customers.

Set the structure and tone once, and each published note follows it. Templates matter more than they sound: they stop one release from reading like a marketing post and the next like a changelog dump. Teams that ship weekly tend to define two, one for major features and one for maintenance.

The changelog lives on your own domain with your logo and colors, and it's searchable. Customers can subscribe by email, so updates arrive without anyone posting links in support threads. This is the part that replaces generic changelog software for most teams.

Build a roadmap from Jira epics, then publish different views for customers, executives, and partners. Access can be fully public, password-protected, or invite-only. You review changes before re-publishing, which keeps an internal slip from appearing on the customer page the moment someone edits a date.

An idea portal lets customers submit requests and upvote what matters. Comments can attach to specific roadmap items, and feedback from the portal, embedded forms, and Slack lands in one inbox. From there you can turn a request into a Jira issue or a Jira Product Discovery insight with the customer context attached.

The app is built on Atlassian Forge, so there's no separate user base to provision. It's SOC 2 Type 2 certified, supports SAML SSO through Atlassian Access, and encrypts data in transit and at rest. Released says data sent to the AI is never used to train models.