You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
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.
Yes, with that option it would need to be a Classic project because Next-gen does not allow you to share schemes, workflows, etc.
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.
Can you provide a screenshot of the existing and the new one? Did you also copy the board?
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.
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.