LogoLogo
👉 Get a free ITSM ebook
Issue Templates Agent
Issue Templates Agent
  • Introduction
    • Welcome to Issue Templates Agent!
    • Template Examples
      • User Story Template
      • Bug Report Template
      • Test Plan Template
      • Employee Onboarding Template
      • Employee Offboarding Template
      • Helpdesk Template
      • Purchase Request Template
    • Best Practices
    • Additional Materials
  • Features
    • Create Templates
      • Basic
      • Simple
      • Advanced
      • Scheduled
      • Save Templates as Drafts
      • Variables
      • Supported Fields
    • Templates on Create Issue View
    • Templates on Issue View
    • Automation and REST API
      • Apply Template on Existing Issue
      • Create Issues with Structure from Template
      • Create New Projects with Issues
      • Schedule Issue Creation
    • Tracking Templates Usage
    • Company vs Team Managed Projects
    • Bulk Edits
    • Template Library
    • Audit Log
    • Import and Export Templates
    • Permissions
  • Resources
    • Security Statement
    • FAQs
    • Related Articles
    • Release Notes
    • Contact our Support
Powered by GitBook

Security

  • Privacy Policy
  • Appsvio Trust Center

appsvio.com © 2025 All rights reserved

On this page
  • Define Clear Templates
  • Use Standardized Naming Convention
  • Include Only Relevant Fields
  • Permissions and Restrictions
  • Consider Multiproject Templates
  • Use Categories for Organization
  • Test Templates Before Deployment
  • Version Control

Was this helpful?

Export as PDF
  1. Introduction

Best Practices

How to make the best out of templates? We have collected some of the best practices below.

Define Clear Templates

Clearly define and create templates for common types of issues or projects in your organization. Templates should include necessary fields. Make sure to add all specific information relevant to the issue or project type.

Use Standardized Naming Convention

Use standardized naming conventions for your templates to make it easy for Jira users to find and select the right template. Include a clear description in the issue template name to convey its purpose.

Include Only Relevant Fields

Include only the necessary and relevant fields in your templates. Too many fields can be overwhelming and may lead to confusion.

Permissions and Restrictions

Set appropriate permissions and restrictions on templates to control who can create or modify them. Ensure that only authorized users can modify or delete templates to maintain consistency.

Consider Multiproject Templates

Keep it simple. If you can, reuse templates for multiple projects instead of duplicating them.

Use Categories for Organization

Organize issue templates into categories based on project type, department, or any other relevant criteria. Make use of Jira's template categorization features to simplify template filtering.

Test Templates Before Deployment

Before making templates available to users, thoroughly test them to ensure they work as intended. Check for any issues with mandatory fields, and default values.

Version Control

If a lot of things change quickly in your organization, be sure to evaluate templates so that they are up to date.

PreviousPurchase Request TemplateNextAdditional Materials

Last updated 2 months ago

Was this helpful?