What this template is for
Beta programs fail when onboarding is ad-hoc - one customer signed an NDA, another didn’t, a third never got training, a fourth gave brilliant feedback that vanished in a Slack DM. This template makes each beta enrolment a tracked Jira issue with explicit gates for legal, provisioning, training, and feedback collection.
It is built for product and customer-success teams running structured betas, not open beta sign-ups.
When to use it
Use this template every time you enrol a customer in a closed or invite-only beta. Skip it for public betas or free-tier opt-ins where the entire experience is self-serve; those should be tracked at the program level and instrumented in the product itself.
How to set it up in Jira
Create a beta-program project. Add the custom fields above to the Create Issue screen. Configure Custom Fields so the Beta Program select list matches the launch Epics in your roadmap. Link each enrolment to the parent launch Epic for rollup reporting.
Sub-task breakdown
- Verify eligibility keeps the cohort tight enough to produce signal.
- Send and countersign the NDA is the legal gate.
- Provision environment prepares accounts, flags, or tenant setup.
- Run the kickoff ensures the customer knows how to use the beta and what feedback you need.
- Weekly check-ins prevent silent attrition.
- Beta exit review captures whether the customer becomes a reference, a case study, or a churn risk.
Use STM Issue Templates to auto-create these sub-tasks for every new beta enrolment.
Fields to add to your Jira create screen
These are the fields a project admin should make sure exist on the Create Issue screen for this issue type (Project settings → Screens). Without these on the screen, reporters can't provide the information triage needs - and STM can't reference them either.
| Field | Example value | Required |
|---|---|---|
Summary | Beta enrol - Acme Corp - AI Summarisation v1.0 | Yes |
Beta Program (custom) | AI Summarisation v1.0 | Yes |
Customer / Account (custom) | Acme Corp | Yes |
Primary Contact (custom) | Jamie Patel, Director of Ops | No |
Eligibility Verified (custom) | Yes / No | No |
NDA Signed Date (custom) | 2026-05-20 | No |
Environment Type (custom) | Customer prod / sandbox / dedicated tenant | No |
Feedback Cadence (custom) | Weekly check-in for 6 weeks | No |
Success Criteria (custom) | 10+ summaries created, 3+ feedback sessions | No |
Component/s | beta-program | No |
Labels | beta-ai-summary, 2026-q3 | No |
Attachments | Signed NDA, kickoff deck, feedback log | No |
Note on custom fields. STM currently supports up to 5 custom fields per template. You can add as many custom fields as you like to your Jira Create Issue screen - the 5-field limit only applies if you want STM to set or update those custom fields itself.
Sub-tasks STM creates automatically
Build an STM sub-task template containing the items below, then wire it to an On Create Issue Executor scoped to this issue type. Whenever a new issue of this type is created in the project, STM creates the full sub-task set in one step - with assignee, due date, and components inherited from the parent unless you override them.
- Verify eligibility against the beta criteria
- Send and countersign the NDA / beta agreement
- Provision the environment and accounts
- Run the kickoff and training session
- Run weekly feedback check-ins
- Run the beta exit review and offboarding
Common questions
What is a Jira beta program enrollment template?
It is a Jira task that captures every step of onboarding a single beta customer onto a program. It tracks eligibility, NDA, environment provisioning, kickoff training, recurring feedback sessions, and exit review. Using one issue per beta customer makes the program operationally measurable - how many onboarded, how many active, how many converted.
How do you run a beta program in Jira?
Create a beta-program project, then file one Jira issue per enrolled customer using this template. Link each enrolment issue to the parent launch Epic. Use the sub-task list to ensure every beta customer goes through the same onboarding gates. Track aggregate beta metrics on a dashboard filtered by the Beta Program field.
Should the beta program template be one issue per customer or one per cohort?
One issue per customer is the right grain because each beta customer has their own NDA, environment, and feedback cadence. Use a parent Epic for the program itself if you want a cohort-level view. The per-customer issue keeps operational accountability clear; the Epic gives you the program rollup.
How do you automate beta onboarding sub-tasks in Jira?
Use STM Issue Templates to attach the six-step sub-task list to every newly created beta-enrolment issue. Configure an Executor on Issue Created when the issue type is Beta Enrollment. That guarantees no beta customer is enrolled without an NDA and feedback cadence step explicitly tracked - see /stm/ for the configuration pattern.
Automate the sub-tasks with STM
STM Issue Templates saves the sub-task list above as a reusable template and creates them on every new issue of this type - via an Executor on issue creation, on status transition, or triggered manually from the issue's "Create bulk sub-tasks" menu. STM does not change the parent issue's create screen (that's a Jira project-settings job) but it removes the manual work of creating the sub-tasks every time.
Try STM on the Atlassian Marketplace ↗ See how STM templates are built →