Components of a Project Templates

Project Template is essentially a set of configurations within Atlassian products and apps ecosystem.

A Project Manager creates a new project from an appropriate project template based on the type of product a customer purchased and what is the rollout process for this specific product, deliverables, milestones, phases, etc.

Project created of a template can be customized based on each specific situation, such as adjusting the timeline based on resources availability, adding customization related tasks, etc.

However, customization should be limited to the extend in which project management methodology is followed with consistency, allowing for accurate reporting.

Here is an example of Project Templates Set for Lead to Cash process lifecycle. Different templates are used by different stakeholders and at different stages of the lifecycle. At the same time, these templates within a set are deeply interconnected and work together to produce the required data for further analysis.

Jira core configurations are always included into a project template of any kind:

1. Record Types (= custom issue types), defined by

   1. issue type screen scheme

   2. custom fields and context

   3. data points captured along the record lifecycle

2. Workflow(s) for each record type, defined by

   1. statuses and

   2. transitions and transition screens

3. The list of configurations may vary from case to case.