Best Practices

Follow these best practices to maximize efficiency, maintain clarity, and ensure a smooth experience when using Easy Issue Templates for Jira Data Center.

1. Define Only the Relevant Scope

   • Keep templates focused on specific use cases to avoid clutter.

   • Although our app supports global templates, it's best to create tailored templates for specific projects, issue types, or teams to ensure relevance and improve usability.

   • Enable Only Needed template Fields to keep issues concise, reliable, and fault-free.

2. Use Clear and Consistent Naming

   • Name templates in a way that clearly describes their purpose (e.g., “Bug Report - Critical” instead of just “Bug Template”).

   • Use prefixes or categories if managing multiple templates (e.g., “Dev - Feature Request” vs. “Support - Incident Report”).

3. Leverage Dynamic Variables for Flexibility

   • Use dynamic variables <<variableName>> for templates that require contextual data instead of static values.

   • Ensure templates remain adaptable to different users and scenarios.

4. Keep Descriptions Clear and Actionable

   • Write clear instructions in the issue description to guide assignees.

   • Use Markdown formatting to highlight key details, steps, or links.

5. Regularly Review and Update Templates

   • Audit templates periodically to remove outdated ones and improve clarity.

   • Adjust fields and content based on evolving team needs and feedback.

6. Manage Access and Permissions Wisely

   • Restrict template editing rights to prevent unwanted modifications.

   • Share relevant templates with the right teams or users to maintain efficiency.

7. Train Your Team for Maximum Adoption

   • Provide documentation or internal guides on how to use templates effectively.

   • Organize short training sessions to onboard team members.

   • Ensure team members know where to find templates and how to apply them.

   • Share our (AppLiger’s) contact details for support in case of questions or issues.