Templates spread. The first ten are useful to everyone. By the hundredth, an HR template shows up for engineers, and a customer reply meant for billing gets used in the wrong space. The fix is to show each template only to the people who need it.
Both of our template apps let you do that.
Work item templates
In AppsDelivered Templates, you can restrict a template to specific users or groups. People outside those groups can’t apply it. That’s useful for:
- HR templates, such as onboarding or a disciplinary process, limited to HR
- Security templates, such as incident response, limited to the security team
- Admin templates that create work across spaces, limited to Jira admins
Comment templates
In AppsDelivered Comments, comment templates belong to groups. A group can limit its templates by three things:
- Space. The billing replies only show in the billing space.
- Work type. The bug replies only show on bugs.
- User group. The escalation replies only show for senior agents.
When a template doesn’t fit, it’s hidden from the list, or its Apply button is turned off. Agents see a shorter list that only holds what they can use.
Pair restrictions with ownership
Every template should have an owner who keeps it current. Restrictions decide who can use a template. Ownership decides who fixes it when the process changes. The History page in AppsDelivered Templates shows who created and changed each template, so you can find the owner when you need them.
Short, relevant lists are what make templates feel helpful instead of noisy.



