Release Templates

Create custom form templates for different release types, teams, or projects

What Are Release Templates?

Templates define the structure of the Create Release form. Each template specifies which sections and fields appear, what’s required, and how the form is organized. Admins can create multiple templates tailored to different release types, teams, or projects — giving each group exactly the input fields they need.

Built-in Sections

Every template includes these built-in sections (some can be toggled on/off):

Section	Contents	Can Toggle?
Release Configuration	Environment, Team, Project, Work Type	No (locked)
Release Information	Service name, Version, Rollback version, Planned date	No (locked)
Release Notes	Rich text summary of changes	Yes
Linked Tickets	Jira tickets grouped by category	Yes
Jira Ticket Settings	Labels, due date sync, priority	Yes
Approval Chain	Approver selection per level	No (locked)

Template Scope — All vs Specific

Each template can be scoped to control where it appears:

All Teams / All Projects — The template is available globally. Any team or project can use it when creating a release.
Specific Team — The template is restricted to a single team. It only appears in the template picker when that team is selected.
Specific Project — The template is restricted to a single Jira project. It only appears when that project is selected.

You can combine scopes — for example, a template scoped to both a specific team and a specific project will only appear when both match.

Planning Calendar & Template Selection When creating a release from the Release Planning Calendar, the calendar pre-fills the team and project based on the date/context you clicked. The template picker then automatically filters to show only templates that match that team and project. If a team-specific template exists, it appears instead of the global one — ensuring each team always gets their own tailored form.

Custom Sections & Fields

Admins can add custom sections with custom fields to capture any additional information their process requires. This makes each template fully flexible — you decide what data to collect for each type of release.

Field Type	Description
Text	Single-line text input
Text Area	Multi-line text
Rich Text	Formatted text with bold, italic, lists
URL	URL input with validation
Link	Named link (label + URL)
Date	Date picker
Dropdown	Select from predefined options
User	Jira user picker
Yes/No	Checkbox toggle
Number	Numeric input with optional min/max
Ticket(s)	Jira issue key picker

Creating a Template

Go to Templates

Navigate to Admin > Templates in the sidebar. Click "+ Add Template".

Name and describe the template

Give it a clear name (e.g., "Standard Release", "Security Hotfix"). Optionally add a description.

Configure mapping

Choose "Available for all" or restrict to a specific team/project. Restricted templates only appear when the matching team or project is selected.

Toggle built-in sections

Enable/disable Release Notes and Linked Tickets based on your needs. Configure linked ticket categories.

Add custom sections and fields

Click "+ Add Custom Section" and define fields. Each field has a label, type, required flag, and placeholder.

Full control for admins Admins decide exactly which fields appear in each template. Need a “Rollback Plan” rich-text field for production releases but not for staging? Create two templates with different custom sections. Need a “Security Review URL” only for the security team? Scope a template to that team and add the field there.

Default Template

Mark one template as Default. This template is auto-selected when creating a new release. At least one template must exist and one must be the default.

Template Selection

When creating a release, the template dropdown shows templates available for the selected team/project. If only one template matches, it’s auto-selected. The template is locked during editing — you cannot switch templates on an existing release.

Example Setup

“Standard Release” — Scoped to All Teams / All Projects. Used as the default template with standard fields.
“Security Hotfix” — Scoped to the Security team. Includes a custom “CVE Reference” URL field and “Impact Assessment” rich text.
“Mobile Release” — Scoped to the Mobile project. Includes custom fields for “App Store Version”, “Build Number”, and “TestFlight Link”.