Convince My Boss
Reusable templates for the sets of issues your team creates over and over.
Jira has no built-in way to save a set of issues as a template. Every onboarding, every release checklist, every recurring piece of work gets rebuilt by hand, or cloned from an old ticket and edited until it is right. That is slow, and it is inconsistent, because whoever builds it decides what goes in.
Below are two emails you can copy, adjust and send.
Informal Email
Subject: A quick win for the tickets we recreate every time
Hi [Recipient’s Name],
Hope you’re doing well.
Every time we run one of our repeatable processes, somebody rebuilds the same set of Jira tickets by hand, or clones an old one and edits it. It takes a while and we end up with slightly different checklists depending on who set it up.
There is an app called STM Lite from Redmoon Software that fixes it:
- Save a set of issues as a template. Sub-tasks, linked issues and epics, defined once and reused.
- Consistency by default. Everyone gets the same checklist, so steps stop being skipped because someone forgot they existed.
- Lightweight. It does the templating part without a lot of setup, which suits us if we only need a handful of templates.
More here: STM Lite.
If we later need automatic creation on transitions or field changes, there is a full STM version we can upgrade to without re-authoring the templates.
Best,
[Your Name]
Formal Email
Subject: Recommendation to adopt STM Lite for repeatable Jira issue sets
I hope this message finds you well.
I am writing to recommend STM Lite from Redmoon Software to reduce manual effort and improve consistency in our recurring Jira processes.
Jira provides no native mechanism for saving a structured set of issues as a reusable template. In practice our teams either recreate the same issue sets manually or clone a previous instance and amend it. Both approaches consume time on every occurrence, and both allow the content of the process to drift, since the person creating the issues effectively decides what the checklist contains.
STM Lite addresses this:
- Reusable templates. A defined set of sub-tasks, linked issues or epic issues can be created repeatedly from a single template.
- Process consistency. Recurring work follows the same defined steps regardless of who initiates it, which matters where those steps carry a control or compliance purpose.
- Reduced setup time. The effort of assembling routine work is removed from every occurrence.
- A clear upgrade path. If we later require automatic creation triggered by issue creation, transitions or field changes, the full STM Issue Templates product covers that, and moving up is a licensing change rather than a migration.
Further detail: STM Lite.
For a security review, the app is Cloud only. Our Cloud Security Statement and Data Processing Agreement set out where data is held and how it is processed.
I would suggest we trial it against one repeatable process and measure the setup time saved.
Best regards,
[Your Name]