Custom Jira Project template; How to clone board from "Create New Project" window?

Hi all,

We have JIRA cloud solution. Not sure what version it is.

Yesterday, I created a customized project with all the settings, fields, screens, permissions, Kanban board, etc., and saved the project as "MY COMPANY PROJECT TEMPLATE" (for example).

Now, I would like all new projects to use everything about this template.

Question #1:

Is it possible for me to have my custom project "template" show within the "Create Project" modal window?

Screenshot 2016-01-22 09.02.45.png

Question #2:

When I use the "Create with shared configuration", see screenshot above, I am able to choose my "template" project to use for my new project, but unfortunately, this technique does not copy the kanban board settings. sad

What is the best way to include my Kanban board settings from another project (i.e., my project "template")?

Question #3:

Is it possible for me to create an option similar to the "Kanban software development" (as seen above) that will create a project and a Kanban board all in one fell swoop?

Honestly, I just want to click a button and have it create a project, with a board included (like Kanban option in above screenshot) and start working.

Optimally, I'd like to not have a project "template" lingering around just so we can use it as a default starting point.

---

Hopefully that all makes sense. Please let me know if I can clarify any of my questions. Thanks a bunch in advance!

10 answers

So, here's my workaround to this issue:

  1. From the Projects dropdown, choose "Create project"
  2. From modal window, at the bottom, click the "Create with shared configuration" link and click "Next"
  3. Choose an existing project (the settings from your chosen project will be used for your new project) and click "Next"
  4. Enter in the new project's details and click submit
  5. Create a "test" issue within your new project (this will allow you to make sure your configuration is working as you go through the following steps)
  6. Navigate to an existing Kanban board
  7. Under the "Board" dropdown, choose "Copy"; JIRA will then take you to the new board's "General" configuration page
  8. On the "General" page of the configuration section, give a name to your new board
  9. Next, click the "Edit Filter Query" link
  10. On the filter query search page, click the "Advanced" link
  11. Edit the filter query so that it searches for your new project's issues … Example query (replace MR with your project's key):

    project = MR ORDER BY Rank ASC
  12. Click the search magnifying glass icon (you should see the test issue we created above)
  13. IMPORTANT: Click the small down arrow next to the "Save" button and choose "Save as" (if you click "Save", you will overwrite the filter query and this will affect the board you copied it from)
  14. In the modal window, name your new filter (I like to name it after the project and the project's Kanban board so they are all named the same)
  15. Once saved, click the "Boards" dropdown and navigate to your newly created board
  16. On the new board's page, click "Board" and choose "Configure"
  17. On the "General" page of the configuration section, click the "Edit Filter Shares" link
  18. Give a name to your filter share (again, I like to name my project, Kanban board, filter query, etc. the same name)
  19. For the "Add Shares" choose "Project", choose the related project name and choose "All"; click the "+ Add" button
  20. Click "Save"

Pheeeew, I think that's all the steps!

Note: It is helpful to have a project and Kanban board "master template" to use for the "copy" steps above.

So yah, that's my workaround. Not sure if there's a more streamlined process.

Optimally, I would want the ability to click one button and be done! As you can see above, having to jump through all those hoops is not optimal.

Possible bug alert:

We have noticed that "Users and roles", found in "Project Settings", do not copy from the previous project. This may or may not be an issue for you. It could be problematic for users that need their project restricted to certain groups. The best suggestion I have is to check this section, after you're done with the above steps, to make sure it's locked down based on your project's requirements.

 

Thanks - this is similar to what I've found too.  It's very manual but it gets the job done.  I haven't had a chance to explore the Gaia plugin yet but it seems like it might help our use case - https://marketplace.atlassian.com/plugins/ca.nuum.gaia/server/overview

Thanks for taking the time to document the granular steps above - it has helped me and will help others.

Glad to help! Thanks for taking the time to comment and share links. Also, thanks for tip on Gaia plugin, taking a look now. smile

omg @Micky Hulse I wish I had've found this 2 weeks ago!  Through trial and error and going down (many) rabbit holes in the documentation and community I came up with pretty much the same workaround, but thanks for the detailed steps - I see now how to set up the filter for a board a bit better, thank you!! :)

We'd like this functionality too.  The Kanban board is an integral part of the project for us.  Being able to create a new project with our preferred settings, board configuration, etc, would be a valuable time-saver.

seems such an obvious requirement, not sure why they don't have this

Hi Micky et all,

 

thanks for this work around, we too want to just be able to duplicate a master project with settings/configuration and board carried across.

 

We also wanted to have master issues (for those recurring tasks on every project) set up as part of the master project and board which we struggled with (most efforts resulted in the tickets still being under the master project or both master and new project).

 

After some trial an error we found that this works (though we haven't yet used it for a real project, only a couple of tests so far) in case of any use to the rest of you;

 

21. From master project, go to Issues and select 'View all issues and filters'.

22. Hit the export (down arrow in top left corner) button and select 'Export Excel CSV (all fields)' to save out CSV file of all issues (this can be done as a one off as oppose to each time you need to copy the master issues).

23. Go to your new project (duplicated from master), then go to Issues and select 'View all issues and filters'.

24. Hit the options button (... button in top left corner), select 'Import issues from CSV' and find the exported CSV file.

25. Select import settings incl your new project and map all possible fields (for some reason we don't seem to have a list of fields that tally even though the file was exported by Jira).

26. Confirm map values.

27. Viola! Your new project now have the master issues which can be moved into the duplicated board.

 

That elusive one button to do these nigh 30 steps would indeed be very handy...

Interesting, master issues I had not thought of using before! Thanks so much for the extra steps and inspiration (I'll be looking into how to utilize master issues).

Our pleasure, without your work around on the first part we would have hit a brick wall so just happy if we can provide something in return.

@Micky Hulse thanks for your workaround unfortunately it doesn't work in the new jira experience.

Does anybody else have a workaround? Currently I have to create a new board and set it up for every project.

This is pretty bad, because we have to create every board from scratch.

(Replying on phone) A few things have moved around (at least, last time I made one a few months back). Off the top of my head, one of the bigger changes is the “copy board” is now only in the overall list of boards (look in the ... menu). I will look at my notes, when I get into work today, and post an updated step-by-step.

In the new Jira experience the quickest way we've found to copy  a board is click

  • Search icon
  • View all boards
  • Three dots next to default board
    • We have a board with the required settings and columns etc to use as a template
  • Copy
  • Edit filter query and location to place it under a specific project etc

If anyone has a quicker way let us know!

Thanks! Works, hope a faster solution will be available in an update.

Thanks @Tom Rogers That was the answer I was looking for.  I wish your solution was at the top! :)

@Ali Arvanaghi this issue is really about how to duplicate a project and board via a defined template. In terms of answers, it's part of the puzzle for the original question. Also, what @Tom Rogers said above, that's what I was trying to get at in my phone reply; they moved the board copy to the official board list. The other thing that changed is the new "People" section found in a project’s settings ... I think this section used to be called “Users and Roles”. Other than that, the instructions above should still work.

We're experiencing this problem too.

Also having problems when trying to share a configuration between two Service Desk projects - It makes up Request Types that aren't in the original project instead of cloning the ones that are.

Hi Paul! Thanks for showing interest in my question.

In regards to getting an existing kanban board to be associated with a new project, here’s my theory:

  1. Duplicate an existing project via the "create with shared configuration" link (in the new project modal window).
  2. View all kanban boards and "copy" desired kanban board to create a duplicate.
  3. Edit the kanban board copy’s configuration and assign a new "filter query" which would grab issues from your new project.

I'm not even sure if the above is even a halfway decent solution as I have not had time to test step #3 above. Even if the above steps do work, this is not optimal workflow.

We would like the ability to create a project with all of our desired settings in one single step. smile

We noticed today, when creating a new project using the "create with shared configuration" link, the new project creates a "Default software scheme" permission scheme, and not the permission scheme assigned to the project it was copied from (in this case, I had assigned "Default Permission Scheme" to the template "starter" project). Not sure if we're doing something wrong here, or if that's a bug (too)? Unfortunately, the "Default software scheme" has barely any restrictions … Not good if you are trying to keep projects hidden from certain users/groups.

Hi Micky, did you ever find a solution to this?  I'm looking to do the same thing.  Thanks.

Hi, we need these functionalities at my organisation too... 

@Scott Falbo Not really. I was able to boil it down to several (annoying) steps though. I will post an answer with less-than-optimal workaround.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

53 views 0 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you