Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Project Template

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

3 answers

1 accepted

1 vote
Answer accepted
John Funk Community Leader Nov 05, 2019

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. 

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 Community Leader Nov 05, 2019

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

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 Community Leader Nov 05, 2019

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.

John Funk Community Leader Nov 06, 2019

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. 

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. 

 

template_workflow.jpg

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

78 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you