Release Studio for Jira

1. Install the app from the Atlassian Marketplace.
2. Go to Settings > Apps > Release Studio (Jira administrators only) and review the templates.
3. Open a project and select the Releases tab. It may be under Morein the project's tab bar.
4. The latest released version and the first template are selected, and the release notes appear at once. Select Copy Markdown, Copy text or Copy HTML.

Only Jira administrators can change templates and settings. Everyone who can use Jira can read templates, so don't put confidential information in them.

1. Pick Versions. You can pick several versions of the project. Or use All versions released since and a date. To add versions from another project you can see, pick it under Add versions from project, then pick its versions under Versions. Release records are saved per project, so Freeze release record is turned off while versions from another project are selected.
2. Pick a Template. Set Language if you want AI text in another language.
3. The text appears in Release notes text. You can edit it there: copying, publishing and freezing use your edited text, and the leak guard checks your words again. Reset text brings back the generated text. Changing the versions, template, language or AI text also starts again from the generated text.
4. Read the warnings:
   • "{n} work items are not done yet."
   • "{n} items may be internal. Review before publishing to customers."
   • "This selection has more than 2,000 work items. Only the first 2,000 are included."
   • "No work items in this selection match the template."

With AI off, the same selection and template give the same text, unless the template uses {{today}}.

• Improve with AIrewrites the notes as readable text for the template's audience and tone.
• Translate writes the notes in the language you set.
• Every sentence the AI writes must point to a work item in your selection. The app removes sentences without a valid source and shows "{n}sentences removed: no matching work item." It also tells you if work items aren't mentioned in the AI text.
• Large selections are split into parts of 40 work items. If a part fails, you see "{n}parts of the AI text could not be created" and those work items are listed as not mentioned. If AI fails, your release notes are unchanged.
• The app sends the work item key, its text (at most 1,500 characters), work type, labels and components to Atlassian's AI. It sends no names, reporters or assignees.
• Always read the text before you publish it.

• Freeze release recordsaves the final text, the work item keys and their status, the template, the time and who froze it. The record can't be edited or deleted by users.
• If the template requires approval, the record shows Waiting for approval until a project administrator or Jira administrator selects Approve. Then it is Final.
• The Release records tab lists the records for the project. Everyone who can see the project sees the list. Only project administrators, Jira administrators and the person who froze a record can open it: select Export and choose Markdown or JSON. The export has a SHA-256 checksum. The tab shows Checksum verified when the content matches it.
• A Final record with Checksum verified can be published to Confluence from the Release records tab. The page has exactly the frozen text.
• Each record keeps the account ID of the person who froze it and of the approver. Names are not stored.
• A record that is too large (about 200,000 characters) can't be saved. Use fewer versions.
• To correct a mistake, freeze a new record. Old records stay until the retention period ends or the app is uninstalled.

In Rovo chat, pick the Release Studio agent and write, for example:

• "Create customer release notes for the latest version."
• "Translate the release notes for version 2.4 to German."
• "Publish the internal release notes to Confluence."
• "What was released and approved for version 1.0?"

The agent lists versions, creates the notes from your templates, and mentions warnings. It shows you the text before it publishes, and publishes exactly that text. If the text would be different when it publishes, it shows you the new text and asks again. That happens when work items were added to or removed from the version, when their text changed (without AI), when someone else publishes it, or, with AI, when more than an hour has passed. It publishes only after you confirm the space and, if there are warnings, confirm them. If the template requires approval, the agent uses the newest final release record for the version. The agent can open release records only for people who may open them on the Release records tab. AI is used only when you ask for it. Selections over 40 work items skip the AI step in the agent; use the Releases tab for those.

Add the step Generate release notes or Publish release notes to Confluence to a rule.

Example: Version released → Publish release notes to Confluence.

• Project key: {{version.projectId}}. This trigger doesn't fill {{project.key}}, so use the project id.
• Version: {{version.name}}.
• Fill in Template, Language and the Confluence space key. Leave Version empty to use the latest released version.
• The first time, the rule owner has to select Connect to let the app act for them. The step runs with the permissions of that person.
• Turn on Publish even if there are leak warnings only if you want warnings to be ignored.
• Publish release notes to Confluence works only without Improve with AI, because nobody reads the text first. With AI turned on, the step stops with ai-requires-review.
• If the template requires approval, the step publishes the newest final release record for the version, or stops with approval-required.
• The rule shows an error in its audit log if the page can't be created, for example without permission in the space.

• A selection includes at most 2,000 work items.
• AI works on parts of 40 work items. The Rovo agent and Automation steps run AI only for up to 40 work items.
• A release record is limited to about 200,000 characters.
• The app works in company-managed and team-managed projects and in dark mode. I haven't tested it on mobile.

• Atlassian doesn't allow apps to write to the clipboard from a normal app page. Copy buttons use a small frame; if copying fails in your browser, select the text in the box and press Ctrl+C.
• Templates, settings and records are stored in Atlassian's Forge hosted storage. Uninstalling the app deletes them. Pages published to Confluence stay.

Release Studio uses 4 scopes: read work, app storage, read Confluence spaces and create Confluence pages. It has no admin scopes and sends no data outside Atlassian. AI runs inside Atlassian. It stores release records, including the account IDs of the people who froze and approved them, for the retention period you choose, and it reports these account IDs to Atlassian's personal data reporting service every week. Logs contain IDs, status codes and AI token counts, never work item content. See our privacy policy: https://www.helkrypt.no/privacy/apps.

• Runs on Atlassian. No data leaves Atlassian.
• AI (Forge LLMs) runs inside Atlassian. No other AI provider.
• 4 scopes, no admin scopes: read work, app storage, read Confluence spaces, create Confluence pages.
• Release records contain release notes text, work item keys and status, and the Atlassian account IDs of who froze and approved them. You choose how long they are kept (default 7 years).
• Logs contain IDs, status codes and AI token counts, never work item content.

Email support@helkrypt.no. Please include your Jira site URL and the project key and version where something didn't work as expected. Don't send work item content.