Project Template

[Marc Spescha]

Hi,

I am testing if Jira Software (Cloud) could be of use in our case as Civil Engineers. We work with many Projects witch are all mostly identically in forms of project-settings - Sprints - epics - tasks - subtasks and so on.. 

Therefore it would be nice when we create a new project we could chose from a own-made template, let's say: Streetproject, Building, Bridge and so on. The templates should initialize predifined issue types settings. Even Sprints, Epic definitions and Tasks are mostly the same, so also those should be within the templates.

Do you have any suggestions how we could manage this? Thanks in advance

[John Funk · Accepted solution]

Hi Marc - Welcome to the Atlassian Community!

One suggestion is that you create a base (or template) project that has all of the desired schemes attached to it, including issue types and workflows. Then when you create a new Project, simply use the Advanced function and base it on an existing Project (one of the base/template) projects. 

You could then use an add-on such as Automation For Jira to create all of the issues (i.e. Epics, Tasks, Sprints, etc.) needed. 

[Marc Spescha]

Hi, thanks for the quick response. 

Alright, i didn't saw that option because my first test-project ist a next-Gen project. It seems only to be possible with classic project. Have to look up what's the difference.

Alright, i installed the add-on an will try it now :) 

[John Funk]

Yes, with that option it would need to be a Classic project because Next-gen does not allow you to share schemes, workflows, etc. 

[Julian Dumitrascu]

How do I find up-to-date information?

I'd like to create some sites from scratch, without any project template, issue type, or workflow created by Atlassian.

[Alistair Morrison]

Kanban Task Template Hack

We've been using this hack on our Kanban board and are pretty happy with it. 

If you have recurring tasks with the same recurring sub-tasks, you can make a template system as follows. 

• In your workflow, create a status called Template, but do not add any transitions to it
• On your team Kanban board, leave off issues with status = Template
• Create a special board that only shows Templates in your project
• Temporarily change your workflow to allow all issues to transition to Template
• On your Template board, create a task and all of the necessary subtask. Include generic descriptions and assign each subtask to the correct person
• Switch your workflow back to having no Transitions to Template status
• Team members can now use the Template board to clone a Template task and its subtasks. Because your workflow does not allow issues to transition to Template status, they will be added to your backlog. 

[Marc Spescha]

yet another question.

When i create a new Project from an existing, using scrum, why isn't the backlog and sprint sites not shown at the left?

[John Funk]

Can you provide a screenshot of the existing and the new one? Did you also copy the board?

[Marc Spescha]

Thanks for your continuous help. I realized that i better first have a look at the different project-types to find out which one suits best for our company. As written, we are Civil Engineers, we have mostly predefined processes. Also we have about 20 people working across different projects at the same time. Even if i like scrum, i don't know if it's easy and intuitiv to use for our case.

May i ask what you think would fit for our needs? Thanks again.

[John Funk]

Most of our teams use Kanban and not Scrum. Scrum provides for batching several pieces of work together, developing them in the same time period and deploying the finished products together. 

Kanban is continuous improvement, continuous delivery - as each card gets finished, it is deployed. So you are encouraged to limit your work in progress and use a pull system.