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

[mhulse]

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. 

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!

[Andrew Feller]

Why is this the answer instead of someone saying the feature should be built into all Agile boards?  Story points are just another mechanism for estimation, so there is no reason why the estimates on tickets couldn't be used for prediction purposes.  I'm going to very disappointed if this continues to be the way Atlassian addresses product demands.

[Deleted user]

i dont see the answer above, its a blue box. what was the answer?

[Martin Suntinger]

One option I've seen several users apply is to set the plan to story points, and configure also the Kanban teams as "Scrum" in Portfolio, with a 1 week iteration length. Then based on the Kanban teams' throughput estimate a "velocity" for how many points are achieved in a week and use this for longer term planning. 

For a rough roadmap, it does not matter that much if the Kanban team's forecast is on a weekly cadence, or day-to-day as long as the rough capacity and throughput is right. 

[Phill Fox]

An extension to the solution proposed by @Martin Suntinger is to create both a Scrum and Kanban board for the same project. Then you can manage issues through both approaches.

A couple of configuration changes I would recommend though are as follows.

1. Change the configuration of the Kanban board card and detail views to show Story Points.
2. Add a quickfilter to remove all items from the Kanban board that have a sprint allocated 
   image2015-12-20 22:32:35.png
   you could also make this part of the filter for the board if you never want to see items that have been allocated to sprints.

By doing the above you will be able to quickly see the Story Points and use it for understanding the workload at any point in time. However, this will not on its own allow you to report or plan with Story Points it will just give you visibility during the actual day-day activity.