Creating a new project with settings from an existing one seems to create a bug tracking project

[Sven Delmas]

I am creating a new project and choose to use an existing classic Kanban project as template. However, the resulting project is not presenting as a Kanban project, but instead as a classic bug tracking project.

That seems to make the use of preexisting projects to kickstart project setups useless unless one wants to change the type of the new project to classic bug tracking.

[Mohamed Benziane]

Hi,

I just try it and it's works fine. 

kanban project

my classic project

Or are you talking about the shared configuration feature ?

[Sven Delmas]

Yes... shared settings... or as I put it "using an existing project as template". New projects work fine, but I want to assign the preexisting schemes etc. from a different project, and the resulting project is not presenting as a Kanban project.

[Adriano]

Same problem here.

[Mohamed Benziane]

It seems that the better way is to open a request https://support.atlassian.com/

Everything looks fine here :

https://jira-software.status.atlassian.com/

[Sven Delmas]

I doubt this is a stability issue (relating to your status link). This seems like a fundamental flaw in how new projects are created. Generally speaking the control and consistency on how that is done seems to be lacking. I have similar issues with automated project creation through CSV, where the project type is always traditional bug project. It seems that in many places there is no proper control about what project template to use and it just defaults to classic.