📚 Glossary

Learn the basics Jira terms connected to issue templates.

Jira issue template glossary:

1. Jira issue template: a predefined structure for creating issues (tasks, stories, bugs, etc.) with consistent fields. Templates help standardize the information captured for different types of issues.

2. Issue Create View: in the context of project management or issue tracking systems, the issue Create view refers to the interface or page where users can input information to create a new task, problem, or any other unit of work that needs to be addressed within a project. To create an issue, click Create in the top navigation.

3. Template Library: a collection or repository of pre-designed templates that can be reused across various projects. A template library streamlines the process of creating consistent and standardized documents, designs, or structures.

4. Category: a label that you can assign to your templates for easier filtering. This feature is made only for managing templates and is visible only in the template library. The end user can't see it.

5. Multiproject templates: relating to or involving multiple projects. You can assign one template to multiple pairs: project and issue type.

6. Issue Type: in project management, an issue type refers to a distinct category or classification assigned to different types of tasks, problems, or work items. Common examples include bugs, tasks, and user stories.

7. Epic: in agile project management, an epic is a large and high-level body of work that is broken down into smaller, more manageable tasks or user stories. Epics typically represent major features or themes within a project.

8. Story: in agile development, a user story is a concise description of a desired feature or functionality from an end user's perspective. It serves as a way to express requirements in a user-centric manner, facilitating communication between development teams and stakeholders.

9. Subtask: a smaller, more specific unit of work that contributes to the completion of a larger task or issue. Subtasks are often used to break down complex tasks into manageable parts for better tracking and management.

10. Parent template: the main template that is applied on the Create Issue screen.

11. Child template: a template used to create an automatic whole structure, for which the use of a "parent template" is a trigger, such as a list of subtasks.

12. Default template: a template that is saved as default for a partial pair of a project and an issue type. It's automatically applied on the Create Issue screen when a user enters this project.

13. Variables: variables are symbolic names or placeholders used to represent and store data values. They are used to manipulating and storing information, creating issues and scheduling them.

14. Jira admin: a Jira Administrator, often referred to as Jira Admin, is an individual responsible for the configuration, customization, and overall administration of a Jira instance. This role involves managing user permissions, workflows, schemes, and configurations to ensure the effective use of Jira within an organization.

15. Bug report template: standardized issue format to systematically capture and communicate information about bugs identified during testing or usage. It typically includes specific sections for details such as the bug's description, steps to reproduce, expected behavior, actual behavior, severity, and any supporting files or screenshots.

16. Jira story template: a predefined structure designed to create user stories within Jira project management. User stories, commonly used in agile development, clearly describe a feature or functionality from an end user's perspective.