STM Lite for Small Teams

One-click sub-task templates for Jira Cloud - no Executor configuration, just a 'Create from template' button on the issue.

Product: STM Lite Audience: Small Teams
Get STM Lite on the Marketplace ↗

Why this matters for small teams

Small teams have a process problem that bigger automation tools solve poorly. The standard sub-task breakdown is real - even a 5-person team agrees that bugs should have triage / fix / test sub-tasks - but the team doesn’t have spare hours to configure Automation rules or wire up Executor chains. The configuration cost has to be less than the time saved.

STM Lite hits that ratio. Setup is: define a template, save it. Use is: click “Create from template” on the issue, pick the template, done. There’s nothing to configure beyond the template itself, and there’s no scheduled trigger to debug.

The trade-off is that the trigger is manual. If a small team is OK with “the reporter clicks the template button” being a habit, STM Lite is the right scope. If the team has grown past that and the manual click is itself the friction, STM (full) is the upgrade path that adds Executors.

Where small teams typically use templates

In practice, the templates that get the most use in small teams are:

  • Bug triage - 3-5 sub-tasks that get applied to most filed bugs.
  • Story implementation - 4-6 sub-tasks for design / build / test / docs / release.
  • Release week - 5-10 pre-release checklist items.
  • Customer escalation - 3-4 acknowledgement-and-resolution sub-tasks.

That’s typically the entire template set a small team needs. STM Lite is sized for that surface area specifically.

What small teams are dealing with today

  • Small teams want consistent sub-task breakdowns but don't have time to configure Executors or Automation rules.
  • Manual sub-task creation is forgotten when the team is under deadline.
  • Confluence docs that describe the 'right' breakdown aren't enforced.
  • Jira Automation works but is over-engineered for a 5-person team's needs - each rule takes longer to configure than the time it saves.
  • Bigger sub-task automation apps include features (Executors, transition triggers, multi-Executor conditions) that small teams will never use.

How STM Lite helps small teams

Sub-task templates

Save a list of sub-tasks as a named template - summaries, descriptions, default assignees. Reuse across any parent issue type.

Manual 'Create from template' button

Every Jira issue gets a 'Create sub-tasks from template' menu item. Pick a template, click apply, sub-tasks created. No rule configuration.

Project-scoped or global templates

Templates can be project-specific or shared globally across the Jira site. Small orgs typically use global templates so the same QA breakdown applies in every project.

Inherit-from-parent defaults

Sub-tasks inherit assignee, due date, and labels from the parent unless overridden in the template - the safe default for ad-hoc creation.

Use cases

  1. Sprint planning breakdown. On Monday morning, the team picks 8 stories. Apply the Story Implementation template to each. The sprint board fills with the standard sub-task set in 5 minutes.
  2. Bug triage. New bug ticket created. The reporter clicks 'Create from template -> Bug Triage' and the standard triage / investigation / fix / regression sub-tasks appear.
  3. Customer-escalation handling. Support agent escalates a ticket to engineering. Apply the Customer Escalation template to get acknowledgement / investigation / resolution / customer-update sub-tasks.
  4. Release-week tasks. Pre-release checklist as a template. Apply to the release ticket once per release; the standard pre-release sub-tasks appear without anyone having to remember them.

Common questions from small teams

What's the difference between STM and STM Lite?

STM (full) supports Executors that auto-trigger templates on issue creation, status transition, or JQL match. STM Lite is manual-trigger only: a user clicks 'Create from template' to apply a template. STM Lite is simpler, cheaper, and a fit for teams that don't need automatic triggering.

Can STM Lite trigger automatically on issue creation?

Not in the Lite tier. For automatic triggering (on creation, on transition, by JQL filter), the full STM app is the upgrade path. Many teams start with STM Lite, prove the value of consistent sub-task breakdowns, then upgrade to STM when the manual click becomes the friction point.

How is STM Lite different from Jira Automation's create-sub-task action?

Jira Automation is one rule per sub-task. STM Lite treats the *set* of sub-tasks as a single template - ordered list, defaults per sub-task, field inheritance. For 2-3 sub-tasks the two are comparable; for larger breakdowns STM Lite is much faster to set up.

Is STM Lite only for Jira Cloud?

Yes. STM Lite is a Cloud-only listing. Data Center customers should use STM (full), which has Cloud and Data Center support.

Can templates be shared across users?

Yes. Templates can be made available to specific projects, specific roles, or globally to the whole site. Common pattern: project lead creates the templates, everyone in the project sees and can apply them.

Try STM Lite for your team

STM Lite works for small teams on Jira Cloud and Data Center. Install from the Atlassian Marketplace, or read the main STM Lite page for the full feature list.

Try STM Lite on the Atlassian Marketplace ↗   See the full STM Lite overview →

Also built for

STM Lite solves a different problem for each team: